Ext Ops Panel
Open dashboard
Comparison

Close vs io.github.nubiia-dev/mcp-quipu

Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.nubiia-dev/mcp-quipu is an MCP server published by nubiia-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceCloseio.github.nubiia-dev/mcp-quipu
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 131
Downloads/week (npm): 24
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

Close vs io.github.nubiia-dev/mcp-quipu
FactCloseio.github.nubiia-dev/mcp-quipu
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.close.com/mcp)On your machine (@nubiia/mcp-quipu)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/nubiia-dev/mcp-quipu
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Close

In its own words, on Docker MCP Catalog:

Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.

io.github.nubiia-dev/mcp-quipu

In its own words, on Official MCP Registry:

Quipu API integration with 18 MCP tools for invoices, expenses, contacts and Spanish VAT reporting

How to run each

Close As a remote MCP server

Claude Code
claude mcp add --transport http close https://mcp.close.com/mcp

Requires: CLOSE_API_KEY (secret)

io.github.nubiia-dev/mcp-quipu As a local MCP server: npm package

Claude Code
claude mcp add --env "QUIPU_CLIENT_ID=<YOUR_QUIPU_CLIENT_ID>" --env "QUIPU_CLIENT_SECRET=<YOUR_QUIPU_CLIENT_SECRET>" --env "QUIPU_OWNER_SLUG=<YOUR_QUIPU_OWNER_SLUG>" --transport stdio mcp-quipu -- npx -y @nubiia/mcp-quipu

Requires: QUIPU_CLIENT_ID (secret), QUIPU_CLIENT_SECRET (secret), QUIPU_OWNER_SLUG

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 Close asks for

  • CLOSE_API_KEY (secret)

Only io.github.nubiia-dev/mcp-quipu asks for

  • QUIPU_CLIENT_ID (secret)
  • QUIPU_CLIENT_SECRET (secret)
  • QUIPU_OWNER_SLUG

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

What it can do: Close · What it can do: io.github.nubiia-dev/mcp-quipu · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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