Frappe MCP Server vs Foxmayn Frappe CLI
Frappe MCP Server is an MCP server published by muthanii. Marketplaces we read that list it: 1 (Official MCP Registry). Foxmayn Frappe CLI is an MCP server published by nasroykh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Downloads/month (PyPI): 174 Downloads/week (PyPI): 81 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.21.1 Forks (GitHub): 6 Stars (GitHub): 16 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Frappe MCP Server | Foxmayn Frappe CLI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 16 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 6 (better) |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (frappe-mcp-server) | On your machine (https://github.com/nasroykh/foxmayn_frappe_cli/releases/download/v1.21.1/ffc_1.21.1.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/muthanii/frappe_mcp | github.com/nasroykh/foxmayn_frappe_cli |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Frappe MCP Server
Interact with Frappe/ERPNext sites — document CRUD, search, and whitelisted method calls
Foxmayn Frappe CLI
Read and change documents, reports and workflows on Frappe and ERPNext sites.
How to run each
Frappe MCP Server As a local MCP server: PyPI package
claude mcp add --env "FRAPPE_API_KEY=<YOUR_FRAPPE_API_KEY>" --env "FRAPPE_API_SECRET=<YOUR_FRAPPE_API_SECRET>" --env "FRAPPE_URL=<YOUR_FRAPPE_URL>" --transport stdio frappe-mcp -- uvx frappe-mcp-server
Requires: FRAPPE_API_KEY (secret), FRAPPE_API_SECRET (secret), FRAPPE_URL
Foxmayn Frappe CLI
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Foxmayn Frappe CLI publish no settings it asks for, so we do not compare settings.
What it can do: Frappe MCP Server · What it can do: Foxmayn Frappe CLI · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.