Labsco
MCP SERVER

Read and write any ERPNext DocType, including the submit and cancel steps its document workflow insists on, without a tool per business object.

ERP & Vertical Business SystemsVerified
Summary
A custom DocType is reached the same way a Sales Invoice is.

Because the eleven tools are DocType-generic, nothing has to be added when your instance grows a new document type — get_doctype_fields tells the assistant what that record accepts before it writes one. call_method is the escape hatch for everything CRUD does not name, reaching any whitelisted Frappe method on the server.

What it is

A generic ERPNext and Frappe client. Eleven tools operate over any DocType: discover which exist, read their fields, query documents, create and update them, and move them through the submit and cancel lifecycle.

What you get
  • The DocTypes your instance actually has, and the field list for any one of them
  • Documents queried by DocType with filters, a chosen field set and a limit
  • A single document fetched whole, child tables and linked data included
  • Documents created and updated from a JSON payload
  • The submittable workflow: submit sets docstatus to 1, cancel sets it to 2, and a cancelled document is amended into a corrected copy rather than edited
  • Permanent deletion, with submitted documents required to be cancelled first
  • ERPNext reports run by name with filters
  • Any whitelisted Frappe server-side method called directly, with arguments as a JSON body or as query parameters
Requirements

A running ERPNext instance reachable at the address you put in ERPNEXT_URL, and npx on your PATH.