Frappe MCP
Provides permission-aware tools for interacting with a Frappe v15 instance, executing under the user's own Frappe roles and User Permissions, with read-only mode by default.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Frappe MCPshow me my open purchase orders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Frappe MCP
A permission-aware remote Model Context Protocol server for Frappe v15.
Each person connects with their own Frappe account. The server issues MCP-only tokens and executes tools under that person's normal Frappe roles and User Permissions. Client applications never receive the person's ERP password.
Endpoints
MCP:
/api/method/frappe_mcp.api.handleAuthorization:
/api/method/frappe_mcp.oauth.authorizeToken exchange:
/api/method/frappe_mcp.oauth.tokenProtected-resource metadata:
/.well-known/oauth-protected-resourceAuthorization-server metadata:
/.well-known/oauth-authorization-server
Related MCP server: Frappe MCP Server
Install
cd /home/frappe/frappe-bench
bench get-app https://github.com/TrueDevs-Inc/frappe-mcp.git
bench --site your-site.example install-app frappe_mcp
bench --site your-site.example set-config frappe_mcp_enabled true
bench --site your-site.example migrate
bench build --app frappe_mcpThe two /.well-known URLs must be routed to the corresponding Frappe methods
by the site's reverse proxy. See docs/operations.md.
Connect
See docs/connect.md for Claude and ChatGPT setup.
Security
Tokens are accepted only by the MCP endpoint.
Authorization codes and access tokens are stored as hashes.
Authorization Code with PKCE S256 is mandatory.
The OAuth
resourcemust exactly match the configured MCP endpoint.Frappe permissions are re-applied to every tool call.
This project is experimental. Test with non-administrator accounts and harmless records before enabling it for production workflows.
Write tools are hidden and mcp:write authorization is rejected unless an
operator explicitly sets frappe_mcp_write_enabled to true. Keep the default
read-only mode until cross-user permission tests pass.
This server cannot be deployed
Maintenance
Related MCP Connectors
- odooOAuthcom.odooconsole
Odoo ERP for AI agents: hosted OAuth endpoint, gated writes, one endpoint for every instance.
Connect any AI assistant to Odoo 16–19 via OAuth 2.0 + PKCE. 400 free calls, no local install.
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
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.238 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with ERPNext data and functionality through the Model Context Protocol, including document CRUD, report running, and API method calls.MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM clients to securely read and write Frappe/ERPNext data under a real user's permissions, with audited calls and granular access control.AGPL 3.0