Frappe MCP Server

Frappe MCP Server is an MCP integration. Interact with Frappe/ERPNext sites — document CRUD, search, and whitelisted method calls.

Packages and local setup

The published pypi package is frappe-mcp-server, version 1.2.0. Its declared MCP transport is stdio.

The package declares FRAPPE_URL (required): Base URL of your Frappe/ERPNext site, e.g. https://your-site.erpnext.com; FRAPPE_API_KEY (required): Frappe API key for token-based authentication; FRAPPE_API_SECRET (required): Frappe API secret paired with the API key; FRAPPE_VERIFY_SSL: Set to 'false' to skip TLS certificate verification. Defaults to 'true'.; FRAPPE_TIMEOUT: Per-request timeout in seconds. Defaults to 30..

The published oci package is docker.io/muthanii/frappe-mcp:1.2.0. Its declared MCP transport is stdio.

The published oci package is ghcr.io/muthanii/frappe-mcp:1.2.0. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.