ERPNext MCP integration for AI agents.
Connect AI agents to ERPNext through 9 structured actions, including get document, create document, and delete document. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ERPNext integration exposes
The ERPNext Agent App exposes 9 provider-backed actions for productivity and finance work. Its current contract lets an authorized agent get one erpnext document by doctype and name, create one erpnext document for the specified doctype, and delete one erpnext document by doctype and name. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ERPNext account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ERPNext capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_documentREADGet one ERPNext document by DocType and name.
INPUTS: doctype / name
create_documentWRITECreate one ERPNext document for the specified DocType.
INPUTS: doctype / data
delete_documentHIGH IMPACTDelete one ERPNext document by DocType and name.
INPUTS: doctype / name
get_document_countREADGet the count of ERPNext documents that match an optional filter.
INPUTS: doctype / filters
get_document_valueREADGet one ERPNext field value or a group of field values without loading the full document.
INPUTS: doctype / name / filters / fieldname
get_logged_userREADGet the currently authenticated ERPNext user for the configured connection.
list_documentsREADList ERPNext documents for a DocType with optional field selection, filters, sorting, and pagination.
INPUTS: doctype / fields / filters / order_by / start
set_document_valueWRITESet one field value on an ERPNext document and return the updated document.
INPUTS: doctype / name / fieldname / value
update_documentWRITEUpdate selected fields on one ERPNext document.
INPUTS: doctype / name / fields
INPUT CONTRACTS
Know what the action needs before it runs.
get_document
doctypeOPTIONAL- The ERPNext DocType name to operate on.
nameOPTIONAL- The unique name of the ERPNext document.
create_document
doctypeOPTIONAL- The ERPNext DocType name to operate on.
dataOPTIONAL- The document fields to create or update in ERPNext.
delete_document
doctypeOPTIONAL- The ERPNext DocType name to operate on.
nameOPTIONAL- The unique name of the ERPNext document.
get_document_count
doctypeREQUIRED- The ERPNext DocType name to operate on.
filtersOPTIONAL- Filters passed through to ERPNext as JSON.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Document
Get one ERPNext document by DocType and name. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_documentControl Create Document
Create one ERPNext document for the specified DocType. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_documentVerify with Get Document Count
Get the count of ERPNext documents that match an optional filter. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_document_countSAFETY BOUNDARY
Operate ERPNext with explicit limits
- Authorize ERPNext with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_document` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ERPNext rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ERPNext task completed successfully.
CONNECTION MODEL
API key
ERPNext API key used with token authentication. Generate it from the user record's API Access section as described in the Frappe REST API docs: https://docs.frappe.io/framework/user/en/api/rest
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ERPNext.