Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Final POS – Custom POS Builder
Overview
Description from the maker (original English)
Build custom POS apps with any AI agent: checkout flows, kiosks, payment terminals. Plus store ops.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Online shops & payments
- You need to fill in: Authorization
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- Can do 60 things (tools) get_connection, list_packs, find_tools, call_tool …
- You fill in yourself:
Authorization
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http final https://ai.finalpos.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"final": {
"url": "https://ai.finalpos.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"final": {
"type": "http",
"url": "https://ai.finalpos.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
Authorizationsecret HTTP headerOptional. Clients with OAuth 2.1 sign in with Final and need no header. Otherwise: Bearer fai_... connection key from https://ai.finalpos.com/connections
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
get_connectionWho this connection acts as: organisation, user, the company Hub tools act on and the companies you may switch to, the allowed and listed packs, and how to reach tools that are not listed.
list_packsEvery tool pack with its product, description, tool count and whether it is allowed for this connection and listed right now.
find_toolsSearch every allowed pack for tools by what you want to do ("low stock", "create a product", "deploy the app"). Returns matching tool names with their pack, whether they are listed and whether they change data. Run a read-only match with call_tool and a write with call_write_tool
call_toolRun a read-only tool from any allowed pack by its full name (for example hub_find_low_stock) without it being listed. Only tools that read are accepted; tools that change data run through call_write_tool. Arguments follow that tool's own input schema, which find_tools returns.
call_write_toolRun a tool that creates, changes, deletes, sends or deploys from any allowed pack by its full name (for example hub_update_product) without it being listed. Only tools find_tools marks as writes are accepted; read-only tools run through call_tool. Arguments follow that tool's own
enable_packsAdd packs to tools/list for this connection (remembered). Only allowed packs can be listed; the client refreshes its tool list.
disable_packsRemove packs from tools/list for this connection to keep the list short. Tools stay reachable through call_tool and call_write_tool.
ask_finaiHand a task in words to Finai, Final's own AI agent, and get its finished answer. It runs as this connection's user on its company, within the allowed packs, and uses Final's tools itself (looking records up, creating products, building or deploying an app). Use it for multi-step
switch_companyChoose the company Hub tools act on, by id or name (get_connection lists them). Remembered on this connection.
flow_apply_blueprint_widgetsCOPY vetted blueprint widgets into a flow as real files — byte-exact, no transcription. Pass picks of { blueprintId, widgetId } (from list_blueprints / search_blueprints); the widget files land under src/widgets/ / with their command-frame plumbing intact, persisted as a restorab
flow_apply_upstream_updateApply the update reviewed with get_upstream_update. Pass resolutions: exactly one entry per conflict — { path, contents } with the COMPLETE merged file, or { path, delete: true } when the file should not exist. Missing, unknown or ambiguous entries fail the whole call with nothin
flow_connect_chatAttach this agent session to an EXISTING flow as a chat in the builder's rail (so the flow's owner sees your work alongside their own chats). Also use log_message to narrate what you're doing.
flow_create_custom_tableCreate a new custom data table (schema: name + typed columns) in your Final organization. USE THIS for any data the app must keep — loyalty stamps, waitlists, bookings, inventory logs, settings: the platform syncs the table to every station running the flow and keeps it working o
flow_create_flowCreate a new, empty flow (app build) in your Final organization for YOU to write the app into. It appears in the Miami builder immediately, with this agent session attached as a chat. Optional theme knobs seed the live palette. Optional `device` ("mobile", "kiosk", "iphone", …) s
flow_create_flow_from_blueprintCreate a NEW flow that starts as a complete, vetted application rather than an empty file tree — the fastest path to a working build when an FBB (a Final Business Blueprint: a whole app) matches what the user wants. For an app the user merely DESCRIBED, use start_build (the websi
flow_delete_flow_filesRemove files from a flow's tree by path. Engine-owned paths are rejected. Recorded as a checkpoint + chat note like writes.
flow_deploy_flowDirect deploy for CI/agent workflows: builds the app in a server sandbox (npm install + vite build) and publishes the dist to Final web-hosting as a new live version. Two things stop a deploy: a failing build, and a hardcoded credential (a build is distributable to other companie
flow_get_blueprintINSPECTION ONLY — read a blueprint's overlay code by id (from list_blueprints) to understand how it works. To USE a blueprint, apply it: apply_blueprint_widgets for a widget-set (materializes its widgets byte-exact with the command-frame plumbing intact AND provisions the custom
flow_get_preview_statusAuthoritative server-side health probe of the flow's preview sandbox, plus a short snapshot of recent dev-server logs (useful to diagnose a red screen or crash).
flow_get_scaffoldThe contract every Final flow app is built against: which files the ENGINE owns (never write them — they are re-asserted verbatim), the baseline package.json (Vite + React 19 + TS + Tailwind + command-frame), the rules your files must follow, and the runtime contracts that compil
flow_get_upstream_statusHas the build this flow was copied from released a newer version? Covers both a "Make it yours" clone of a listing and a build started from an FBB. Returns update.status: "available" (a newer deployed release exists — review it with get_upstream_update), "current" (up to date), "
flow_get_upstream_updateReview what an update from the original build would change — the same review the builder shows its maker, shaped for an agent. Returns the releases since the clone, the clean changes (added/changed/removed paths, with full incoming contents for added+changed), and CONFLICTS: file
flow_install_extensionInstall an extension ORG-WIDE: creates the install link on EVERY company in your Final organization (demo companies included), skipping companies that already have it, so it is safe to retry. Installing is deliberate and org-visible — confirm with your user and call this ONLY whe
flow_list_blueprintsList EVERY vetted, type-checked blueprint available to reuse — working functionality (gift cards, loyalty, payment surfaces, product grids, carts, customer views, order tickets, receipts), not just screen layouts. Check the catalog BEFORE creating custom tables or hand-rolling a
flow_list_custom_tablesList your organization's custom data tables with their column schemas. Custom tables are Final's built-in, station-syncing database — data written on one station is automatically synced to every other station running the flow, and keeps working OFFLINE at the point of sale. They
flow_list_extension_custom_tablesList the CUSTOM TABLES an extension registers (table name + typed columns), so generated code can read/write its data at runtime via renderClient.getCustomTableData / upsertCustomTableData by table name (ground the calls with lookup_command_frame). Only the org's OWN extensions e
flow_list_extension_surfacesList the SURFACES an extension exposes — embeddable iframe injection points, each with a surfaceId, a platform (builder/hub/render), a type, and a url. Render an installed surface inside a generated screen with the engine component ` " />` (ground it with lookup_engine_component)
flow_list_extensionsList the platform EXTENSIONS available to your organization — the org's own plus the public marketplace — so you can suggest, inspect, or install one. Each entry carries an id, label, category, short description, and its source (organization or public); public results need no hub
flow_list_flowsList the flows (app builds) in your organization, newest first: id, title, timestamps, and live theme knobs. Final staff sessions also see Final's own flows, marked owner: "Final". Use a flow id with the other tools, or create_flow to start fresh. Clones of listed builds carry an
flow_list_secret_keysList the key NAMES already stored in your organization's encrypted secrets vault — never the values (no tool returns a secret value). Use this to (a) reuse an existing key instead of requesting a new one, and (b) poll whether a request_secret ask has been fulfilled by the human.
flow_log_messageRecord a message in this agent's chat inside the builder — the user's request (role 'user') or your own progress/summary (role 'assistant'). Keeps the builder timeline faithful to what happened in this session.
flow_lookup_command_frameLook up the EXACT, version-locked command-frame API a generated Final POS app runs on: renderClient method signatures + params, CF* entity field lists, pub/sub topic event vocabularies, and worked examples. Pass one of method/entity/topic for a precise lookup, entity+field to con
flow_lookup_engine_componentLook up the exact props/signature of an engine-owned `./final/*` helper: the `@/final/ui` primitives (Button, IconButton, Card, Tile, Input, Field, Chip, ListRow, Dialog, Sheet, Toolbar, Heading, EmptyState, cn) plus usePrint, StationHomeButton, SwitchUserButton, useStationHome,
flow_lookup_pos_apiLook up the Final POS REST API (https://api.finalpos.com) — endpoint method/path, request fields, response shape, and a worked fetch example. This is the ONLINE-ONLY fallback for admin/management operations command-frame cannot express (creating products/variants/categories, cust
flow_open_in_builderThe recommended way to finish: a deep link that opens this flow in the Miami builder, where the owner can review the work, restore checkpoints, and deploy through the Launch tool (validation gates, listing media, changelog, version history).
flow_read_flow_filesRead a flow's generated source tree. Omit `paths` to list all file paths (cheap); pass `paths` to fetch specific files' contents.
flow_rename_flowRename a build (flow) authoritatively across the platform in one call: the builder header, list_flows / open_in_builder, and the Deerlake catalog all reflect the new title, and updatedAt is bumped. A deployed build keeps its hosted web app: the hostname and version history are un
flow_request_secretAsk the flow's owner to enter a third-party credential (API key, auth token, webhook secret) into Final's encrypted vault. THIS TOOL TAKES NO VALUE and no tool ever returns one — the human types it into a masked input in the Miami builder, and it goes straight into the vault. Why
flow_search_blueprintsSEMANTIC search over the vetted blueprint catalog — matches are ranked by what you MEAN, not by shared words, so describe the capability in plain language ('rewards for repeat customers' finds the loyalty blueprint). RUN THIS FIRST — before creating custom tables or hand-rolling
flow_start_previewBoot the flow's server-side preview sandbox (Vite dev server) — or reconcile a running one to the flow's current files — and return its public HTTPS URL already pinned to this flow's mock dataset: the maker's pick, else its vertical's (sushi, not restaurant). Open the URL in a br
flow_stop_previewStop the flow's preview sandbox and free its resources. The next start_preview cold-boots in a couple of seconds.
flow_sync_previewReconcile a (running or cold) preview sandbox to the flow's current files and run the green-build gate (tsc + vite build). Returns the gate result — the fastest way to know your code actually compiles. The engine forces parts of package.json on every sync: the dev/build/typecheck
flow_update_custom_tableEvolve an EXISTING custom data table's schema: add columns, change existing ones (rename/retype — destructive for stored rows, use sparingly), or drop columns. The table is identified by its kebab-case name from list_custom_tables. Tables are ORG-WIDE, so a schema change lands fo
flow_validate_flowDeterministic STATIC checks against the platform contract: (1) guardrails — fabricated renderClient methods, forbidden browser APIs/imports, engine-file writes; (2) a REAL TypeScript check of command-frame usage against the PINNED .d.ts the app installs (the version is stamped in
flow_write_flow_filesCreate or overwrite files in a flow's tree (full contents, not diffs). Engine-owned paths are rejected — see get_scaffold. Every write lands as a restorable checkpoint and is narrated in the builder chat. If a live preview is running, follow up with start_preview to sync it. Vali
hub_add_customer_noteAdd a note to a customer — an allergy, a preference, what happened with an order. Existing notes are KEPT; this appends. Takes the customer ID from get_customers. Staff read these in the cabinet, so write what the merchant said, not your own summary.
hub_add_modifier_choiceAdd one choice to an existing modifier, leaving the rest alone. This is the safe way to extend a modifier — unlike update_modifier, it cannot drop anything. Appends to the end unless sortOrder says otherwise. price is the extra charge per unit as a human amount ("0.70"); omit it
hub_add_product_imagesAdd photos to an existing product — from public URLs, or as base64 bytes when the merchant attached the file itself and there is no URL. URL images are downloaded and stored on the platform, so the product never depends on someone else's site staying up. Existing photos are KEPT
hub_add_tax_rate_to_groupAdd an EXISTING rate to a tax group, or change that rate’s compounding flag within the group. Both ids come from get_taxes. This shares the rate — it does not copy it. The group starts charging the rate’s existing per-outlet percentages, and a later edit to that rate changes this
hub_adjust_stockChange the count of ONE variant at ONE outlet — the cabinet's "Adjust Inventory" action. CONFIRM WITH THE MERCHANT FIRST, repeating the product, the outlet, the reason and the number: this writes immediately, is permanently recorded against the employee in the stock history, and
hub_assign_roleMove a team member onto a different role — this is how someone gains or loses access. Answers 'give Maria access to the reports', 'make him a cashier again', 'take away her permissions'. PERMISSIONS ARE POWER. Confirm with the merchant first, naming the person and the role out lo
hub_cancel_bookingRelease a booked window. The order stays as it is — cancelling a booking is not a refund, and money is never moved here; if the customer is owed money, do that on the order. Confirm with the merchant before cancelling a booking somebody already paid for.
hub_cancel_purchase_orderCancel an order the merchant no longer wants. CONFIRM FIRST, naming the supplier and the PO number — there is no undo, and the order disappears from the list rather than showing as cancelled. REFUSED once any stock has been received against it: that stock is real and the record h
hub_confirm_bookingTurn a hold into a real booking once the order behind it is paid, so it stops expiring. Needs the order the booking was sold on — confirming without one is refused, because a confirmed booking nobody can find on a receipt is worse than an expired hold.
hub_create_booking_resourceAdd one bookable thing to the company directory. Call get_booking_resources first — a resource is reused across every service, so a second "Marco" would split one barber into two calendars and let him be booked twice at once. The name is what staff will see in the calendar.
hub_create_booking_rulesCreate a booking policy. Call get_booking_rules FIRST and reuse a matching set instead — these are shared company-wide, not per product. `weeklyHours` are LOCAL wall-clock times at the outlet; if neither the outlet nor the company has a timezone the engine refuses availability wi
hub_create_categoryCreate a product category. Call get_categories FIRST — a second "Drinks" is easy to make and there is no merge. Pass parentId to make it a subcategory; leave it out for a top-level one. The cabinet's own form asks for a description, so ask the merchant for one rather than inventi
hub_create_customerCreate a customer. Call get_customers with the email or name FIRST — a duplicate splits one person’s order history in two and there is no merge from here. Email is required, exactly as in the cabinet's own customer form. Ask the merchant for anything you do not know instead of in
hub_create_modifierCreate a new question the till can ask, with its choices. THIS ALONE DOES NOTHING AT THE TILL — follow it with link_modifier_to_category, or the modifier sits unused. Choose selectionType carefully, because it CANNOT be changed afterwards: "single" = pick exactly one (milk, cooki
hub_create_outletOpen a new point of sale — the cabinet’s Add Outlet form. Name and the full street address (address, city, state, postCode) are all REQUIRED, exactly as on that form. Do NOT try to set a country: every outlet inherits the company’s country, and it can never be changed per outlet.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain finalpos.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- ✓ Pass
Endpoint responds
Responded in 82 ms (HTTP 200)
- – Not applicable
Sign-in with OAuth
No sign-in needed
- ✓ Pass
No hidden instructions in tool descriptions
Read 60 tool descriptions and found no hidden instructions to the AI
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 2550 servers in this category
- Published to the registry more recently than 60% of the other 2550 servers in this category
- Basic checks equal to or better than 100% of the other 2550 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Final POS – Custom POS Builder safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: Authorization
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.1) reached the registry 20 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Final MCP server: build custom POS apps with AI
Connect Claude, ChatGPT, Gemini, Cursor, Codex or any MCP client to Final :
build custom POS apps with Flow (checkout flows, self-checkout kiosks, payment terminals) and run the store behind them from Hub , through one server.
https://ai.finalpos.com/mcp
Connect · What it can do · Tool reference · FAQ · finalpos.com
The Final MCP server is the official Model Context Protocol server for [Final](https://finalpos.com), the commerce platform for custom point of sale. One remote endpoint, https://ai.finalpos.com/mcp, gives an AI agent access to every Final product the merchant allows:
- Flow, the custom POS app builder: describe a checkout and the agent builds it from vetted screen blueprints, grounded in Final's version-locked POS APIs, then validates it, returns a live preview link and deploys it to payment terminals, tablets and kiosks. Counter POS, self-checkout, restaurant ordering, kitchen displays and in-person payment apps.
- Hub, the back office behind those apps: products and catalog, stock and purchase orders, orders, customers, sales reports, team and roles, outlets, taxes, bookings.
You sign in with your Final account (OAuth 2.1) and choose the company and what the agent may do. There is nothing to install or run locally.
| Endpoint | https://ai.finalpos.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 with PKCE (sign in with Final), or a fai_ connection key as Authorization: Bearer |
| Registry name | com.finalpos/final |
| Acts as | The person who connected it, on one company, within the packs they allowed |
| Cost | Free to connect; what the agent does follows your Final plan, as if you did it in Final |
Connect
Most clients only need the URL. They open a Final sign-in page where you pick the company and the packs, then they're connected.
Claude (claude.ai, Claude Desktop)
Settings → Connectors → Add custom connector, URL https://ai.finalpos.com/mcp.
ChatGPT
Settings → Apps & Connectors → Advanced settings → Developer mode, then Create with the URL https://ai.finalpos.com/mcp.
Claude Code
claude mcp add --transport http final https://ai.finalpos.com/mcp
Run /mcp in Claude Code and choose Authenticate. Or install the plugin, which adds the server together with the Final playbook skill. Inside Claude Code:
/plugin marketplace add Final-Commerce/final-pos-mcp
/plugin install final@final
Gemini CLI
gemini extensions install https://github.com/Final-Commerce/final-pos-mcp
The extension adds the server, the Final playbook and commands: /final-pos:stock, /final-pos:sales, /final-pos:new, /final-pos:preview, /final-pos:validate and /final-pos:deploy. Sign in once with /mcp auth final inside Gemini CLI. To add only the server:
gemini mcp add --transport http final https://ai.finalpos.com/mcp
Cursor
Or in ~/.cursor/mcp.json:
{
"mcpServers": { "final": { "url": "https://ai.finalpos.com/mcp" } } }
VS Code (GitHub Copilot)
Install in VS Code, or:
code --add-mcp '{"name":"final","type":"http","url":"https://ai.finalpos.com/mcp"}'
Codex, scripts and clients without OAuth
Create a connection key at ai.finalpos.com/connections. It is shown once, and the page prints the exact snippet for each client. For Codex, add this to ~/.codex/config.toml:
[mcp_servers.final]
url = "https://ai.finalpos.com/mcp" http_headers = { "Authorization" = "Bearer fai_YOUR_KEY" }
Any other client: POST https://ai.finalpos.com/mcp with Authorization: Bearer fai_YOUR_KEY.
Keys that start with
sk_(Flow) orfpm_(Hub) belong to those products'
own servers and are not accepted here. Create a
fai_key instead, or use OAuth.
Check that it works
Ask your agent: *"Use Final to tell me which company you're connected to and which packs you can use."* It calls get_connection and list_packs.
What your agent can do
Tools are grouped in packs. When you connect you choose which packs the agent may use, and those are also the OAuth scopes. To keep the model's context small, a connection lists only a few packs at a time. The core tools reach the rest: find_tools searches every allowed pack, and call_tool calls any allowed tool by name.
| Pack | Product | What it covers | Listed by default |
|---|---|---|---|
catalog | Hub | Products, variants, categories, options, modifiers, product photos and the media library | ✓ |
inventory | Hub | Stock levels and history, transfers, suppliers, purchase orders, reorder rules, stock CSV import/export | |
orders | Hub | Orders, refunds and e-commerce order sync (read-only: the till takes payments) | |
customers | Hub | Customer records, notes, order history and customer import | |
reports | Hub | Financial summary, sales and payment breakdowns, employee sales, sessions, transactions, record export | |
team | Hub | Team members, roles and permissions | |
store | Hub | Outlets, stations, taxes and Hub extensions | |
bookings | Hub | Bookable services: rules, resources, availability, holds and confirmations | |
build | Flow | Build and deploy Final POS apps: API grounding, blueprints, flow files, preview sandboxes, validation, deploy | ✓ |
build_data | Flow | Custom tables (the app database), the secrets vault and Flow extensions |
Tool names carry their product: hub_get_products, hub_find_low_stock, flow_create_flow, flow_deploy_flow. [TOOLS.md](TOOLS.md) lists every tool, with its pack, whether it changes data, and its arguments.
Core tools (always listed): get_connection, list_packs, find_tools, call_tool, enable_packs, disable_packs, switch_company.
Things to ask
Building custom POS apps (Flow)
- "Build a coffee-shop kiosk with a product grid, modifiers, a cart and card payments, then give me a preview link."
- "Add a tip screen to my counter app and validate it."
- "Create a self-checkout flow for a small grocery store with barcode scanning and a receipt screen."
- "Ship the latest version of my self-checkout flow."
An app build usually runs flow_get_scaffold → flow_create_flow → flow_lookup_command_frame (grounding) → flow_get_blueprint → flow_write_flow_files → flow_validate_flow → flow_start_preview, and returns a live preview URL. Everything the agent builds also appears in the Final builder, where every file write is a restorable checkpoint.
Running the store (Hub)
- "Which products are below their reorder point at the Main Street outlet? Draft a purchase order for the usual supplier."
- "Compare last week's sales by category with the week before."
- "Add these 40 products from the attached spreadsheet, with photos."
- "Who were my top ten customers this month, and what did they buy?"
- "Set up a 45-minute massage as a bookable service with two therapists."
Safety and permissions
- Your role still applies. Every Hub call runs as the person who connected, and Hub checks their live role on each call. Owner-only actions stay owner-only.
- Packs are the permission. The agent can only call tools in the packs you allowed. You can change packs or disconnect at any time at ai.finalpos.com/connections, and disconnecting revokes every token at once.
- Writes are labelled. Read tools carry
readOnlyHint, and deploys and deletes carrydestructiveHint, so clients can ask before acting. The server tells agents to confirm deploys, deletes and bulk changes with you. - Money stays on the till. Taking payments, refunding and voiding orders are not available over MCP.
- Secrets never pass through the model.
flow_request_secretasks you to enter an API key in the builder. - Everything is logged. The Connections page shows each connected client and every call it made, live.
- Flow limits: Flow allows 30 preview boots, 12 builds and deploys, and 300 file writes per hour.
Privacy and support
- What Final keeps. The connection (who made it, the company and the packs), the token it uses to reach Hub and Flow (encrypted), and a log of each tool call: the tool, the outcome, how long it took, and redacted previews of the arguments and result. You see that log on the Connections page.
- What Final doesn't see. Your conversation. MCP clients send tool calls, not the chat around them.
- Disconnecting deletes the stored token and revokes every token issued to that connection.
- Privacy policy · Terms
- Support: support@finalpos.com. For problems with this guide or the plugin, open an issue.
Flow's direct endpoint
Setups made before the gateway may still use https://flow.finalpos.com/api/mcp with a Flow sk_ key (registry name com.finalpos.build/final-flows). It keeps working, but new setups should use https://ai.finalpos.com/mcp, which includes Flow.
FAQ
What is the Final MCP server?
It is the official MCP server for Final POS. One remote URL, https://ai.finalpos.com/mcp, lets an AI assistant read and manage a merchant's Final back office (Hub) and build point-of-sale apps (Flow).
Can ChatGPT or Claude manage my Final POS inventory?
Yes. Allow the inventory pack when you connect. The agent can check stock levels, find low stock, suggest reorders, raise purchase orders and record received goods.
Can an AI agent build a POS app on Final?
Yes. With the build pack the agent creates a flow, writes the app against Final's version-locked APIs and vetted screen blueprints, validates it, and returns a live preview URL. You launch it from the Final builder.
Do I need an API key?
No, if your client supports OAuth (Claude, ChatGPT, Claude Code, Cursor, Gemini CLI, VS Code): just sign in with Final. Codex and scripts use a fai_ key from ai.finalpos.com/connections.
Which company does it act on?
The one you pick when you connect. If your accoun
Only the beginning is shown; read the rest in the repo