Frappe Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRAPPE_DOCS_MAX_BYTES | No | Ceiling on one response, in UTF-8 bytes. 0 disables truncation. | 100000 |
| FRAPPE_DOCS_CACHE_TTL_MS | No | How long fetched pages and the catalogue stay fresh (15 minutes). | 900000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_frappe_docsA | 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. |
| get_frappe_docA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.