ERPNext MCP Server

by yazelin

Overview Schema Source Related Servers Discussions Admin

Python

Remote

create_document

Create a new ERPNext document by specifying the DocType and field values in JSON format.

Instructions

Create a new document.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "doctype": "<doctype>",
      "data": "<data>"
    },
    "name": "create_document"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	JSON string of field values, e.g. '{"customer_name": "Test", "customer_type": "Individual"}'
`doctype`	Yes	ERPNext DocType name

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.5.0May 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / data / description
```
Added value: +"JSON string of field values, e.g. '{\"customer_name\": \"Test\", \"customer_type\": \"Individual\"}'"
```
- addedInput schema / properties / doctype / description
```
Added value: +"ERPNext DocType name"
```
First observedv0.1.0Feb 3, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only says 'create a new document', omitting side effects, permissions, idempotency, error handling, or success criteria. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. However, it could provide more context without becoming overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 params, no annotations, output schema available), the description lacks context about the system (ERPNext), the meaning of 'document', and the creation process. It does not enable an agent to fully understand the tool's role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new document' clearly states the action and resource, but it lacks differentiation from sibling tools like update_document. It is not a tautology since it adds 'new', but it's minimal and doesn't specify the system context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like update_document or submit_document. The description does not mention prerequisites, context, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.