erpnext-fast-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_documentA | Fetch a single document by DocType and name (primary key). Example: get_document("Customer", "CUST-0001") |
| list_documentsA | List/search documents of a DocType. filters: Frappe filter syntax, e.g. [["status", "=", "Open"]] or {"status": "Open"}. fields: list of fieldnames to return, e.g. ["name", "customer_name"]. Defaults to ["name"]. order_by: e.g. "creation desc". limit: max rows to return (default 20). limit_start: offset for pagination. |
| create_documentA | Create a new document of the given DocType. data: field values for the new document, e.g. {"customer_name": "Acme Corp"}. |
| update_documentB | Update fields on an existing document. data: field values to change, e.g. {"status": "Closed"}. |
| delete_documentA | Permanently delete a document. This cannot be undone. |
| get_doctype_metaA | Fetch the field/schema definition (metadata) for a DocType. Useful for discovering what fields exist before create_document/update_document calls. |
| get_countB | Count documents of a DocType, optionally matching filters. |
| run_reportB | Run a Frappe/ERPNext Query or Script Report and return its result. |
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 8 tools
Each tool has a clearly distinct purpose: CRUD operations (list, create, get, update, delete), metadata inspection, counting, and report execution. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern: list_documents, create_document, get_document, update_document, delete_document, get_doctype_meta, get_count, run_report. The use of singular for single-document operations and plural for listing is a sensible convention.
8 tools is well-scoped for a document management server. Each tool covers a necessary operation without redundancy or bloat, fitting comfortably within the ideal range.
The tool set provides full CRUD lifecycle coverage for any DocType, plus useful supplementary tools for metadata discovery, counting, and running reports. There are no critical gaps in the core document workflows.