Final POS Docs vs lu
Final POS Docs is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Final POS Docs is an MCP server published by Final-Commerce. No marketplace we read lists it any more. lu is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 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
| Fact | Final POS Docsno longer listed · | lu |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (docs.finalpos.com/mcp) | On your machine (https://github.com/adelaidasofia/luma-mcp/releases/download/v0.1.0/luma-mcp.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/final-commerce/final-pos-mcp | github.com/adelaidasofia/luma-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Final POS Docs
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Flow's direct endpoint for sk_ keys. For all of Final in one server, use com.finalpos/final.
-
Pine Labs SDK API Documentation MCP Server
List and fetch official Pine Labs SDK API documentation via MCP tools.
-
Clover POS for a single merchant: sales, inventory, orders, customers (reads + safe writes).
-
Discover admitted MERXAT products and check capabilities; payment governed server-side.
-
Read payment settings, orders and receipts, create payment links and API keys.
-
webPosto ERP (management for gas stations and convenience stores) via session capture with your auth
What each says it does
Final POS Docs
Search the Final POS REST API documentation.
lu
lu.ma events MCP server with draft+confirm safety, audit logging, and prompt-injection scrubbing.…
How to run each
Final POS Docs
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
lu As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install luma-mcp@claude-community
Requires: LUMA_API_KEY (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
The marketplaces of Final POS Docs publish no settings it asks for, so we do not compare settings.
What it can do: Final POS Docs · What it can do: lu · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.