Frappe Docs MCP Server
This server provides read access to the Frappe framework documentation via MCP, enabling AI clients to search and fetch pages as clean markdown.
Search: Use
search_frappe_docswith a query (and optionallimit1–50, default 10). Every token must match in the title or path, so adding terms narrows results. Returns matching page titles and paths.Fetch: Use
get_frappe_docwith a path (e.g.,en/tutorial). The server extracts only the article body from the HTML, converts it to markdown, stripping navigation, reducing size drastically (e.g., from ~960 KB to a few KB). Truncates if content exceedsFRAPPE_DOCS_MAX_BYTES.Caching: In-memory caching of pages and catalogue for a configurable duration (
FRAPPE_DOCS_CACHE_TTL_MS). Concurrent requests for the same page share one fetch.Integration: Compatible with any stdio-capable MCP client (VS Code, Claude Desktop, etc.).
Provides tools for searching and fetching documentation pages from the Frappe framework documentation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Frappe Docs MCP Server search Frappe docs for creating a doctype"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frappe Docs MCP Server
A Model Context Protocol server that gives an MCP client read access to the Frappe framework documentation.
It speaks MCP over stdio using the official
@modelcontextprotocol/sdk,
so any stdio-capable client (VS Code, Claude Desktop, Claude Code) can run it.
Tools
search_frappe_docs
Finds documentation pages by keyword. Start here when you do not already know a page's exact path.
Parameter | Type | Description |
| string | Keywords, e.g. |
| number | Optional, 1-50, default 10 |
Every docs page embeds the full navigation tree, so one fetch yields a catalogue of all ~215 pages. Every query token must match somewhere in a result's title or path, so adding a word narrows the results rather than widening them.
1 page matched "create doctype":
- **Create a DocType** — `en/tutorial/create-a-doctype`get_frappe_doc
Fetches a documentation page and returns its readable content as markdown.
Parameter | Type | Description |
| string | Path relative to the docs root, e.g. |
Paths always resolve under https://docs.frappe.io/framework/user. A leading
framework/user is stripped if you include it, .. segments are rejected rather
than resolved, and each segment is percent-encoded, so a path cannot escape that
prefix or smuggle in a query string.
A raw docs page is roughly 960 KB of HTML, most of it navigation. Only the article body is kept and converted to markdown, which brings a typical page down to a few KB.
Related MCP server: CHECK-MODULE MCP Server
Configuration
Both settings are optional. A malformed value is reported on stderr and the default is used, so a typo degrades rather than killing the server.
Variable | Default | Meaning |
|
| Ceiling on one response, in UTF-8 bytes. |
|
| How long fetched pages and the catalogue stay fresh (15 minutes). |
Pages and the catalogue are cached in memory, so repeated lookups within a session do not re-fetch. Concurrent requests for the same page share a single fetch.
Requirements
Node.js 20 or newer. There is no node-fetch dependency; the server uses the
global fetch built into Node 20.
Quick start
git clone https://github.com/muthanii/frappe_docs_mcp.git
cd frappe_docs_mcp
npm install
npm run build
npm testWiring it into a client
The server reads JSON-RPC from stdin and writes it to stdout, so it must be
launched directly rather than through npm run start (npm prints its own banner
to stdout, which corrupts the protocol stream).
VS Code — .vscode/mcp.json is already set up:
{
"servers": {
"frappe-docs-mcp": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/dist/server.js"]
}
}
}Claude Desktop / Claude Code — point at the built entry point:
{
"mcpServers": {
"frappe-docs-mcp": {
"command": "node",
"args": ["/absolute/path/to/frappe_docs_mcp/dist/server.js"]
}
}
}Run npm run build after any source change so dist/ stays current.
Docker
docker compose run --rm -T frappe-docs-mcpThe image publishes no port. This is a stdio server, not an HTTP service, so it must be run attached with a client owning stdin and stdout.
Development
File | Role |
| URL construction and path sanitising |
| Navigation-tree parsing and keyword search |
| Article extraction, markdown conversion, truncation |
| TTL cache with request coalescing |
| Tool registration and the stdio transport |
|
|
Logic is kept out of server.ts so it can be tested without spawning a process.
npm run build uses tsconfig.build.json, which excludes *.test.ts so tests
do not ship in the image. npm test compiles everything, including the tests.
package-lock.json is committed and the Docker build uses npm ci, so image
builds are reproducible.
Diagnostics must go to stderr. Anything written to stdout is interpreted as a protocol frame; CI asserts that the server writes nothing to stdout before a client speaks.
License
MIT
Available Tools
2 toolsget_frappe_docGet Frappe documentation pageA
Fetch a page from the Frappe framework user documentation at https://docs.frappe.io/framework/user and return its readable content as markdown. Paths are relative to that prefix and start with a language segment, e.g. "en/tutorial" or "en/basics/doctypes". Use search_frappe_docs to discover paths.
Inputs: path (required).
search_frappe_docsSearch Frappe documentationA
Find Frappe framework documentation pages by keyword. Returns page titles with the paths to pass to get_frappe_doc. Use this first when you do not already know the exact path of the page you want.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one discovers documentation paths via keyword search, the other retrieves content by path. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern: search_frappe_docs and get_frappe_doc. The naming is predictable and matches the actions they perform.
With only two tools, the set feels slightly thin but is appropriate for a documentation-focused server. The search-then-fetch workflow is minimal yet coherent, and adding more tools might be unnecessary.
For the stated purpose of accessing Frappe documentation, the pair covers the full lifecycle: discovery (search) and retrieval (get). No write operations are relevant, and there are no obvious gaps in the read-only documentation use case.
Maintenance
Related MCP Connectors
Search, browse and read DeveloperHub's own docs. Every docs site on DeveloperHub serves one at /mcp
Search and read public Isotopes AI documentation through MCP.
Query your own PDFs and documents from any MCP client. Every answer cites the page it came from.
Search and manage your team's knowledge from MCP clients.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.3MIT
- AlicenseAqualityDmaintenanceEnables managing internal documentation with search and add capabilities, and fetching official documentation from 13+ popular libraries via MCP tools.69MIT
- AlicenseNot gradedqualityDmaintenanceProvides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.5MIT
- AlicenseAqualityDmaintenanceMCP server providing AI coding assistants with documentation and source code for @gaddario98 React packages, including tools for listing packages, retrieving docs and types, and searching source.5MIT