Documentation Index
Fetch the complete documentation index at: https://developer.prove.com/llms.txt
Use this file to discover all available pages before exploring further.
Prove MCP overview
The Prove Model Context Protocol (MCP) server exposes tools to connected AI clients so assistants can search Prove documentation and read full pages from a virtual documentation filesystem. It complements other doc access patterns such as plain Markdown andllms.txt.
If your team uses AI-powered editors, you can point your client at Prove’s hosted MCP endpoint—no separate Prove package to run on your infrastructure for this service.
Hosted endpoint
Prove hosts an MCP server. Register this URL in your MCP client using that product’s workflow for HTTP MCP servers. Exact steps depend on the vendor; follow their documentation for adding or enabling MCP servers, ensure your network allows HTTPS todeveloper.prove.com, then confirm the prove (or equivalent) server appears connected in the client’s MCP or tools UI.
MCP resources (skill.md)
The MCP server exposes skill.md files as MCP resources so agents discover capability descriptions without installing those files separately. Resources appear in the MCP resource list alongside the tools below.
Tools available to assistants
Tools are exposed to connected AI clients as follows.search_prove
Search across the Prove knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Prove, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.
If you need the full content of a specific page, use the query_docs_filesystem_prove tool to head or cat the page path (append .mdx to the path returned from search — for example, head -200 /api-reference/create-customer.mdx).
Optional parameters for search_prove (when the client passes them through) include:
pageSize— Number of results to return, between 1 and 50; defaults to 10.scoreThreshold— Minimum relevance score between 0 and 1; filters out lower-confidence matches.version— Restrict results to a documentation version tag.
query_docs_filesystem_prove
Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at / that contains only the Prove documentation pages and OpenAPI specs. This is not a shell on any real machine — nothing runs on the user’s computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.
This is how you read documentation pages: there is no separate “get page” tool. To read a page, pass its .mdx path (for example, /quickstart.mdx, /api-reference/create-customer.mdx) to head or cat. To search the docs with exact keyword or regex matches, use rg. To understand the docs structure, use tree or ls.
Workflow: Start with the search tool for broad or conceptual queries like “how to authenticate” or “rate limiting”. Use query_docs_filesystem_prove when you need exact keyword or regex matching, structural exploration, or to read the full content of a specific page by path.
Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run --help on any command for usage.
Stateless calls: Each call is stateless: the working directory always resets to / and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with && or pass absolute paths (for example, cd /api-reference && ls or ls /api-reference). Do not assume that cd in one call affects the next call.
Examples
tree / -L 2— see the top-level directory layoutrg -il "rate limit" /— find all files mentioning “rate limit”rg -C 3 "apiKey" /api-reference/— show matches with three lines of context around each hithead -80 /quickstart.mdx— read the top 80 lines of a specific pagehead -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx— read multiple pages in one callcat /api-reference/create-customer.mdx— read a full page when you need everythingcat /openapi/spec.json | jq '.paths | keys'— list OpenAPI endpoints
rg -C or head -N over broad cat on large files. To read only the relevant sections of a large file, use rg -C 3 "pattern" /path/file.mdx. Batch multiple file reads into a single head or cat call whenever possible.
Rate limits
The following hourly rate limits are used so the service stays available:- Per user (IP address) — 5,000 requests per hour for MCP server configuration queries.
- Search — 10,000 search tool calls per hour for the public MCP path; 5,000 per hour when using authenticated search quotas.
- Query docs filesystem — 10,000 filesystem tool calls per hour for the public MCP path.
query_docs_filesystem_prove described above. If you hit throttling, narrow queries, batch reads, and space out tool calls.