Ext Ops Panel
Open dashboard
Comparison

io.github.FAVIOSENGER/cte-mdfe-mcp vs io.github.codespar/mcp-bling

io.github.FAVIOSENGER/cte-mdfe-mcp is an MCP server published by FAVIOSENGER. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codespar/mcp-bling is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceio.github.FAVIOSENGER/cte-mdfe-mcpio.github.codespar/mcp-bling
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 78
Downloads/week (npm): 78
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.2
Downloads/month (npm): 112
Downloads/week (npm): 24
Forks (GitHub): 52
Stars (GitHub): 274
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

io.github.FAVIOSENGER/cte-mdfe-mcp vs io.github.codespar/mcp-bling
Factio.github.FAVIOSENGER/cte-mdfe-mcpio.github.codespar/mcp-bling
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)274 (better)
Forks (GitHub) (differs)0 (worse)52 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (cte-mdfe-mcp)On your machine (@codespar/mcp-bling)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/faviosenger/cte-mdfe-mcpgithub.com/codespar/mcp-dev-latam
Changes in the last 7 days00
First seen (differs)2026-10-152026-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

io.github.FAVIOSENGER/cte-mdfe-mcp

In its own words, on Official MCP Registry:

Emissao e consulta de CT-e e MDF-e (transporte) no Brasil via Focus NFe, para agentes de IA

io.github.codespar/mcp-bling

In its own words, on Official MCP Registry:

MCP server for Bling — ERP: products, orders, invoices (NF-e/NFS-e), stock, AR/AP, webhooks

How to run each

io.github.FAVIOSENGER/cte-mdfe-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "FOCUS_NFE_TOKEN=<YOUR_FOCUS_NFE_TOKEN>" --transport stdio cte-mdfe-mcp -- npx -y cte-mdfe-mcp

Requires: FOCUS_NFE_TOKEN (secret)

io.github.codespar/mcp-bling As a local MCP server: npm package

Claude Code
claude mcp add --env "BLING_ACCESS_TOKEN=<YOUR_BLING_ACCESS_TOKEN>" --transport stdio mcp-bling -- npx -y @codespar/mcp-bling

Requires: BLING_ACCESS_TOKEN (secret)

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

Only io.github.FAVIOSENGER/cte-mdfe-mcp asks for

  • FOCUS_NFE_AMBIENTE
  • FOCUS_NFE_TOKEN (secret)

Only io.github.codespar/mcp-bling asks for

  • BLING_ACCESS_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.FAVIOSENGER/cte-mdfe-mcp · What it can do: io.github.codespar/mcp-bling · 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