
Frappe MCP Server
io.github.muthaniiPublished by GitHub account muthaniiv1.2.0Updated Oct 27, 2026
Interact with Frappe/ERPNext sites — document CRUD, search, and whitelisted method calls
Overview
Connects an assistant to a Frappe/ERPNext site over its REST API for document CRUD, search, and whitelisted server-side method calls.
- What you can do
- Check connectivity and credentials against the site
- Retrieve a single document by doctype and name
- Search and list documents with filters
- Create, update and delete documents
- Call whitelisted server-side Python methods
- When to use it
- Useful when you work with a Frappe or ERPNext site and want an assistant to look up, edit or create records, or trigger server-side methods, without leaving the chat client.
- Requirements
- Runs locally as a stdio process via uvx, pip, or Docker. Needs FRAPPE_URL (base URL of the site), FRAPPE_API_KEY and FRAPPE_API_SECRET for token authentication, plus network access to the site. Optional FRAPPE_TIMEOUT (default 30) and FRAPPE_VERIFY_SSL (default true).
Installation
In SourceWeft
- Open Frappe MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Frappe MCP Server
[PyPI] [Python] [Docker Hub] [Docker pulls] [GHCR] [MCP Registry] [License]
A Model Context Protocol (MCP) server for Frappe Framework. Connect Claude Desktop, VS Code Copilot, and other MCP clients to any Frappe/ERPNext site via its REST API.
Where to get it
Features
- Document CRUD — get, create, update, delete Frappe doctypes
- Search — full-text and filtered document search
- Remote method calls — invoke any server-side Python method
- Authentication — API key + secret (token-based auth)
- Docker-first — single
docker runcommand, no Python install needed
Quick start
With uvx (no install):
With pip:
With Docker (Docker Hub):
With Docker (GHCR):
Available tools
Every tool ships MCP tool annotations and a declared outputSchema, so a client can tell read tools from destructive ones before calling them.
frappe_run_method is marked destructive because its effect is determined entirely by the method you name.
Configuration
MCP client config
Add this to your claude_desktop_config.json or Copilot config.
Via uvx:
Via Docker:
Local development
License
MIT — see LICENSE.
Source: README.md at commit e1f8986
Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts