Ext Ops Panel
Open dashboard
Comparison

Foxmayn Frappe CLI vs oec.sh

Foxmayn Frappe CLI is an MCP server published by nasroykh. Marketplaces we read that list it: 1 (Official MCP Registry). oec.sh is an MCP server published by oec.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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

Where each is published
MarketplaceFoxmayn Frappe CLIoec.sh
Official MCP Registry Listed
Version: 1.21.0
Forks (GitHub): 6
Stars (GitHub): 16
Not marked · First seen
Listed
Version: 0.3.0
Downloads/month (npm): 471
Downloads/week (npm): 471
Forks (GitHub): 0
Stars (GitHub): 0
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

Foxmayn Frappe CLI vs oec.sh
FactFoxmayn Frappe CLIoec.sh
Marketplaces that list it11
Stars (GitHub) (differs)16 (better)0 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last release (differs)2026-10-22 (worse)2026-10-22 (better)
Where it runs (differs)On your machine (https://github.com/nasroykh/foxmayn_frappe_cli/releases/download/v1.21.0/ffc_1.21.0.mcpb)Remote server (mcp.oec.sh/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/nasroykh/foxmayn_frappe_cligithub.com/oecsh/mcp-server
Changes in the last 7 days (differs)42
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 34 h ago

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

Foxmayn Frappe CLI

In its own words, on Official MCP Registry:

Read and change documents, reports and workflows on Frappe and ERPNext sites.

oec.sh

In its own words, on Official MCP Registry:

Operate your oec.sh Odoo servers, projects and environments with your own API key.

How to run each

Foxmayn Frappe CLI

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

oec.sh As a remote MCP server

Claude Code
claude mcp add --transport http oec-sh https://mcp.oec.sh/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: OECSH_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only oec.sh has a remote endpoint we check. How we check endpoints

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: Foxmayn Frappe CLI · What it can do: oec.sh · 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.

Where the data comes from: how the catalog is built