ERP MCP Server
Provides read-only MCP access to ERPNext data, letting connected agents search DocTypes, inspect fields and child tables, query documents with filters/grouping/aggregation, retrieve documents and child rows, search by text, run allowed saved reports, and execute guarded read-only SQL.
Provides read-only MCP access to Frappe site data with the connected user's permissions, exposing tools for DocType discovery, document queries, saved reports, and guarded SQL while enforcing role, user, and field-level permissions.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ERP MCP Server
Lets outside AI agents (Claude Code, Claude Desktop, Cursor, your own agents) read your ERPNext / Frappe data through the Model Context Protocol (MCP), with the connected user's own permissions.
It is a companion to the AI Assistant app (omni_ai) and needs it installed: the tools, the
permission checks, the SQL guard and the audit log are the assistant's, exposed over MCP.
Works on Frappe / ERPNext v15 and v16, Frappe Cloud, self-hosted and on-premise.
No extra Python packages, no separate process, no extra port: it is one HTTP endpoint on your site.
Read-only. There are no tools that create, change or delete anything.
Does not need an AI provider key: the connecting agent brings its own model.
Install
Install the AI Assistant app first, then:
bench get-app <url-or-path-of-this-app>
bench --site your-site install-app erp_mcpOn Frappe Cloud, add the app to your bench from its Git repository and install it on the site.
Related MCP server: Frappe MCP Server
Switch on
Open ERP MCP Settings.
Tick Enabled. The form shows the Endpoint URL.
Roles: who may connect. It starts as System Manager only.
Choose whether agents may run saved reports and SQL. SQL additionally needs the user to hold a role listed under Roles Allowed to Use SQL in AI Assistant Settings, and the SQL feature to be on there.
Max rows per call (10 to 1000) and Calls per minute per user (0 = unlimited).
Connect an agent
Each person connects as themselves with a Frappe API key: User → Settings → API Access → Generate Keys. The agent then sees exactly what that user may see.
Claude Code:
claude mcp add --transport http erp https://your-site.example.com/api/method/erp_mcp.api.mcp \
--header "Authorization: token API_KEY:API_SECRET"Any client that takes a JSON configuration:
{
"mcpServers": {
"erp": {
"type": "http",
"url": "https://your-site.example.com/api/method/erp_mcp.api.mcp",
"headers": { "Authorization": "token API_KEY:API_SECRET" }
}
}
}Use a dedicated user with narrow roles for unattended agents, and always HTTPS: the header is a credential.
Tools
Tool | What it does |
| Find DocTypes by name or topic |
| Fields, links and child tables of a DocType |
| Filtered, grouped, aggregated reads of a DocType |
| One document with its child rows |
| Search documents by text |
| Saved reports (if allowed) |
| A guarded read-only SELECT (if allowed, for SQL roles only) |
| More rows of an earlier result, by |
Query tools return the first rows plus a result_id; the agent pages through the rest with
get_result_rows. A user's stored results cannot be read by another user.
Safety
Authentication is Frappe's own; a request without valid credentials is refused.
Every call runs as the connected user: role permissions, User Permissions and field-level permissions apply. Password and key fields are never returned. Settings DocTypes that hold credentials are hidden.
Every tool call is written to AI Assistant Tool Log (when logging is on in the assistant).
Record contents can contain text that tries to steer an agent (prompt injection). This server cannot change data, but an agent with other tools could be misled; that is the agent's side to manage.
Data returned by the tools goes to whatever AI model the connected agent uses.
Protocol notes
Streamable HTTP transport with plain JSON responses, protocol versions 2024-11-05, 2025-03-26 and 2025-06-18. No sessions, no server-sent stream (GET returns 405), no JSON-RPC batches.
Only tools are offered; resources and prompts are empty.
OAuth sign-in is not implemented. Clients that can only connect through OAuth (for example connectors added inside the claude.ai web app) cannot use this server; clients that accept a header can.
Licence
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Draxlr's remote MCP server connects AI assistants to your SQL databases and dashboards. Explore schemas, run read-only queries, manage saved queries and dashboards, and export results, all with row-level security so each user sees only their own data.
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
Query your org's data in natural language — read-only MCP access to SQL, NoSQL, files & warehouses.
Related MCP Servers
- AlicenseBqualityDmaintenanceIntegrates with ERPNext/Frappe API to enable AI assistants to create, read, update, and list documents, run reports, and authenticate via the Model Context Protocol.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI models to securely interact with Frappe Framework/ERPNext instances, supporting document CRUD, RPC methods, file management, workflows, reporting, and more via the Model Context Protocol.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with ERPNext data and functionality through the Model Context Protocol, including document CRUD, report running, and API method calls.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to securely read data from customers' ERPNext/Frappe sites through a multi-tenant OAuth-protected gateway, with tools for listing, searching, counting, retrieving, and reporting on documents.-