Frappe Dev MCP Server
Accelerate Frappe and ERPNext work—DocTypes, bench commands, and APIs—with an MCP server pointed at your bench directory.
Overview
Frappe Dev MCP Server is a MCP server for the Build phase that helps agents work with Frappe/ERPNext DocTypes, bench commands, and APIs using your FRAPPE_PATH bench.
What is this MCP server?
- MCP assistance tailored to Frappe/ERPNext DocType and framework patterns
- Covers bench commands and framework APIs from agent sessions
- FRAPPE_PATH env var points at your bench directory (defaults to cwd)
- npm package frappe-dev-mcp-server v1.0.1 with stdio transport
- Title: Frappe Dev MCP Server—niche ERP stack, not generic CRUD scaffolding
- Package version 1.0.1
- Transport: stdio
- npm identifier: frappe-dev-mcp-server
Community signal: 2 GitHub stars.
What problem does it solve?
Frappe developers re-explain bench layout, DocType rules, and ERPNext APIs to agents that lack a structured connection to their local framework.
Who is it for?
Solo builders and small teams already running a Frappe bench who want ERPNext-aware MCP tooling during customization sprints.
Skip if: Founders not on Frappe/ERPNext, greenfield products without a bench install, or low-code users avoiding bench CLI.
What do I get? / Deliverables
After configuring FRAPPE_PATH and stdio MCP, your agent can reason against your bench context for DocType and API tasks with less generic hallucination.
- Agent-guided DocType and framework customization steps
- Bench command and API workflows referenced in MCP sessions
- Faster ERPNext extension iteration from the coding agent
Recommended MCP Servers
Journey fit
Frappe customization is backend build work when solo operators or small teams extend ERPNext apps rather than greenfield React-only products. The server wraps bench-local development primitives via FRAPPE_PATH, making it a backend/integration MCP layer on top of an existing Frappe install.
How it compares
Frappe/ERPNext-specific dev MCP, not a general backend generator or database admin server.
Common Questions / FAQ
Who is frappe-dev-mcp-server for?
Frappe and ERPNext developers using MCP agents who maintain a local bench and need DocType, bench, and API guidance in context.
When should I use frappe-dev-mcp-server?
Use it during build backend work when you are creating DocTypes, running bench commands, or wiring ERPNext APIs with agent assistance.
How do I add frappe-dev-mcp-server to my agent?
Install frappe-dev-mcp-server from npm, set FRAPPE_PATH to your bench directory, and register the package as a stdio MCP server in your client.