ERPNext MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERPNEXT_URL | Yes | The base URL of your ERPNext instance | |
| ERPNEXT_API_KEY | Yes | API key for authentication | |
| ERPNEXT_API_SECRET | Yes | API secret for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_doctypesA | Get a list of all available DocTypes |
| get_doctype_fieldsB | Get fields list for a specific DocType |
| get_documentsA | Get a list of documents for a specific doctype |
| create_documentB | Create a new document in ERPNext |
| update_documentC | Update an existing document in ERPNext |
| run_reportC | Run an ERPNext report |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All DocTypes | List of all available DocTypes in the ERPNext instance |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: create_document and update_document handle document lifecycle operations, get_doctypes and get_doctype_fields provide metadata, get_documents retrieves document lists, and run_report executes reports. The descriptions reinforce these distinct roles, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_document, get_doctypes, and update_document. This predictability makes the tool set easy to navigate and understand, with no deviations in naming style.
With 6 tools, the server is well-scoped for ERPNext operations, covering core document management, metadata access, and reporting. Each tool serves a specific function without redundancy, making the count appropriate for the domain's typical needs.
The tool set provides strong coverage for document CRUD (create, get, update) and metadata access, with run_report adding reporting functionality. A minor gap exists in document deletion, which could limit full lifecycle management, but agents can likely work around this omission.