Advanced MCP
Exposes a Frappe or ERPNext site to AI assistants over the Model Context Protocol — so an assistant can look things up, draft records and produce documents against your live data, instead of guessing.
The problem it solves
An AI assistant is only useful on your ERP if it can see the real thing. Field names on a customised site aren't guessable, DocType names must be exact, and a wrong filter returns a confidently wrong answer. Advanced MCP gives the assistant a way to discover the site rather than assume it — search the DocTypes, describe the fields, then query.
What it can do
| Discover the site | Search DocTypes by keyword and describe any one of them — field names, types, what Link fields point at, which are required. |
| Read records | List with filters, sorting and paging; fetch a single document with its child tables; read one field; count matching rows. |
| Write records | Create drafts, update existing documents, and submit or cancel where the workflow allows it. |
| Reports | Run the site's existing reports and return their rows. |
| Documents | Generate a PDF using a specific print format, and read text out of PDFs already on the site — including cropping to a region of a page. |
| Collaborate | Add comments to documents, so an assistant's findings land on the record itself. |
Permissions are the point
Runs as a real user
Every call executes as the signed-in Frappe user, under that user's own permissions. There is no privileged back door and no separate access model to keep in sync.
Capabilities you control
Reads, writes, and submit/cancel are each grantable. Deletion can be switched off entirely, so an assistant can help without being able to destroy anything.
Bounded responses
A maximum row count per call keeps a careless query from pulling the database, and results state how many rows exist in total so a first page is never mistaken for a complete answer.
Interested in connecting your own site?
Tell us which site you'd want to connect and what you'd want an assistant to do with it.