Foxmayn Frappe CLI — Claude Code MCP server
Connects Claude Code to Frappe and ERPNext sites through an MCP server and CLI. Use it to inspect records, reports and workflows, with controlled write access.
Open on GitHubWhat Foxmayn Frappe CLI does
Foxmayn Frappe CLI connects Frappe and ERPNext sites to AI clients through the REST API. Its MCP layer exposes work with documents, reports, workflows, files and permissions, while the command line can emit JSON, NDJSON or CSV for scripts.
Set up a site with ffc init, using browser sign-in, an API key or a password. Then run ffc mcp install --client claude-code to add the connection to Claude Code. Site policies can narrow access to selected DocTypes and server methods; write commands also support confirmations and dry runs.
The client can be forced into read-only mode with --read-only. Tool calls are written to a local audit log, and deletes, cancellations, workflow actions and shares require approval. Without a completed ffc init login, the server cannot act on a site.
What it helps with
- inspect Frappe DocType records
- export a report as JSON or CSV
- locate open ERPNext tasks
- check the account’s roles and permissions
- apply a change after approval
Example prompts for the agent
- List open records from the
ToDoDocType on the connected site. - Find
Sales InvoiceACC-SINV-2026-00001and show its fields. - Review the reports and workflows available to my account.
How to install Foxmayn Frappe CLI
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Foxmayn Frappe CLI
How do I install Foxmayn Frappe CLI in Claude Code?
On Linux or macOS, install the CLI with curl -fsSL https://raw.githubusercontent.com/nasroykh/foxmayn_frappe_cli/main/install.sh | sh, add a site with ffc init, then connect MCP by running ffc mcp install --client claude-code.
What does Foxmayn Frappe CLI do?
It links AI clients with Frappe and ERPNext sites, allowing MCP and REST API operations on documents, reports, files and workflows.
How can I restrict the MCP server?
Use --read-only, narrow the site policy to permitted resources, and keep approvals for write operations. Calls are also stored in a local audit log.
