Ext Ops Panel
Open dashboard
Comparison

Close vs Final POS – Custom POS Builder

Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Final POS – Custom POS Builder is an MCP server published by finalpos.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceCloseFinal POS – Custom POS Builder
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.1
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 Final POS – Custom POS Builder
FactCloseFinal POS – Custom POS Builder
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-18
Where it runs (differs)Remote server (mcp.close.com/mcp)Remote server (ai.finalpos.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/final-commerce/final-pos-mcp
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)Responded 5 days ago, requires a keynot checked yet

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.

Final POS – Custom POS Builder

In its own words, on Official MCP Registry:

Build custom POS apps with any AI agent: checkout flows, kiosks, payment terminals. Plus store ops.

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)

Final POS – Custom POS Builder As a remote MCP server

Claude Code
claude mcp add --transport http final https://ai.finalpos.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Close 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 Final POS – Custom POS Builder publish no settings it asks for, so we do not compare settings.

What it can do: Close · What it can do: Final POS – Custom POS Builder · 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