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 | No | API key for authentication (optional) | |
| ERPNEXT_API_SECRET | No | API secret for authentication (optional) |
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 | {} |
| resources | {} |
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 targets a distinct aspect: listing doctypes, fetching fields, retrieving documents, creating, updating, and running reports. There is no overlap between these operations.
All tools use a verb_noun pattern (get_, create_, update_, run_), but pluralization is inconsistent: get_doctypes and get_documents are plural, while get_doctype_fields, create_document, and update_document use singular forms.
With 6 tools, the server is well-scoped and covers core ERPNext interactions without unnecessary bloat. Each tool has a clear purpose.
The set covers create, read (list), and update, but lacks a delete_document operation. Also, get_documents only implies listing, with no explicit get by ID, which may require workarounds. Reports add some breadth.