ERPNext MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERPNEXT_URL | Yes | URL of the ERPNext instance | |
| ERPNEXT_DEBUG | No | Enable debug logging | false |
| ERPNEXT_API_KEY | Yes | ERPNext API key | |
| ERPNEXT_API_SECRET | Yes | ERPNext API secret |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticate_erpnextB | Authenticate with ERPNext using username and password (alternative to API key) |
| get_documentA | Get a single document by DocType and name |
| get_documentsB | Get a list of documents for a specific DocType with optional filtering |
| create_documentB | Create a new document in ERPNext |
| update_documentC | Update an existing document in ERPNext |
| delete_documentC | Delete a document from ERPNext |
| submit_documentA | Submit a document (Draft → Submitted). Only works for submittable DocTypes. |
| cancel_documentB | Cancel a submitted document |
| get_doctypesB | Get a list of all available DocTypes in ERPNext |
| get_doctype_fieldsA | Get field definitions for a specific DocType |
| get_doctype_metaC | Get complete metadata for a DocType including all configuration |
| create_doctypeB | Create a new custom DocType in ERPNext |
| add_doctype_fieldC | Add a custom field to an existing DocType |
| create_custom_fieldB | Create a custom field that survives ERPNext updates |
| create_property_setterC | Override a DocType or field property |
| get_workflowB | Get the active workflow for a DocType |
| create_workflowB | Create a new workflow for a DocType |
| update_workflowC | Update an existing workflow |
| run_reportC | Execute an ERPNext report and get results |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| doctypes | List of all available DocTypes in ERPNext |
TDQS
Scored across 19 tools
Most tools are distinct, but get_doctype_fields and get_doctype_meta overlap in scope, and add_doctype_field vs create_custom_field can confuse agents about which to use. Descriptions help but boundaries are not always clear.
Tool names generally follow a verb_noun pattern (get_document, create_document, submit_document), but there are minor inconsistencies such as singular vs plural (get_document vs get_documents) and mixed resource naming (create_custom_field vs add_doctype_field).
At 19 tools, the count is slightly above the ideal 3-15 range but still reasonable for an ERP system covering documents, Doctypes, workflows, and reports. The breadth justifies the number without feeling bloated.
The toolset covers document CRUD, lifecycle actions (submit/cancel), DocType management, customization, workflows, and report execution. Minor gaps exist such as no delete workflow or update custom field, but core workflows are well supported.