For AI agents
The Final Flows MCP server
Final Flows is the MCP (Model Context Protocol) server for the Final commerce platform. Connect it to Claude Code, Cursor, ChatGPT, Codex, or any MCP client, and your AI agent can build a complete point-of-sale app end to end: ground every API call in version-locked catalogs, adapt vetted screen blueprints, write files into a cloud flow with restorable checkpoints, boot a live HTTPS preview, persist data in offline-capable custom tables, run the same validation gates Final's own builder uses, and deploy to real payment terminals, tablets, and kiosk hardware.
Server endpoint
- Endpoint
- https://build.finalpos.com/api/mcp
- Transport
- Streamable HTTP
- Auth
- OAuth 2.1 (authorization code + PKCE) or a static bearer organization API key (sk_…)
- Scope
- Org-scoped — a key or OAuth connection can only touch its own organization's flows
Quick start (no manual setup)
The fastest way to connect is from Build itself: on build.finalpos.com, start a prompt and choose "Connect your own AI (MCP)". Build creates your flow and generates one self-contained block — setup instructions, the server address, a one-time key, and your build brief. Paste that block into your AI tool and it wires up the connection on its own.
Manual configuration
Already have an organization API key? Point your client straight at the server. Keys are minted in Build (chat rail → Connect your AI tool) and shown once — treat them like a database password.
Claude Code
claude mcp add final-flows --transport http https://build.finalpos.com/api/mcp \
--header "Authorization: Bearer sk_YOUR_ORG_KEY"Cursor
{
"mcpServers": {
"final-flows": {
"url": "https://build.finalpos.com/api/mcp",
"headers": { "Authorization": "Bearer sk_YOUR_ORG_KEY" }
}
}
}Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global).
Codex CLI
[mcp_servers.final-flows]
url = "https://build.finalpos.com/api/mcp"
http_headers = { "Authorization" = "Bearer sk_YOUR_ORG_KEY" }Codex has no static-header flag on `codex mcp add`, so configure it in ~/.codex/config.toml.
ChatGPT
Settings → Apps & Connectors → enable developer mode → Create
Connector URL: https://build.finalpos.com/api/mcpChatGPT (and claude.ai custom connectors) use OAuth 2.1: you'll be asked to sign in to your Final account and approve access — no key to paste.
Tool catalog
Every tool is org-scoped. Read tools are annotated read-only; writes and deploys are marked destructive so clients can ask before acting.
Grounding (read-only)
Version-locked catalogs so the agent writes code against real Final APIs instead of guessing.
lookup_command_frameDocs for the command-frame API: renderClient, entities, and topics, locked to the platform version.lookup_pos_apiThe Final POS REST API catalog.lookup_engine_componentProps and usage for the built-in ./final/* engine helper components.list_blueprintsVetted screen blueprints (with their widgets) available to copy from.search_blueprintsSearch the blueprint catalog by capability or keyword.get_blueprintRead-only inspection of a single blueprint.get_scaffoldThe flow scaffold: engine-owned paths, baseline package.json, and contract rules.
Flow lifecycle
Create flows and edit their files. Every write is a restorable checkpoint, mirrored into the Build chat.
list_flowsThe organization's flows, newest first.create_flowNew empty flow plus an external chat session; returns a builder deep link.connect_chatAttach the agent session to an existing flow.log_messageNarrate work into the flow's builder chat.read_flow_filesList a flow's file paths, or fetch specific files.write_flow_filesWrite files into the flow tree; engine paths are rejected, and each write creates a checkpoint.delete_flow_filesDelete files from the flow tree.apply_blueprint_widgetsCopy blueprint widgets into the flow byte-exact; returns a manifest.
Custom tables & secrets
Custom tables are Final's built-in station-syncing, offline-capable database — the sanctioned persistence for flows. Secret values never pass through the agent.
list_custom_tablesThe organization's tables and their column schemas.create_custom_tableCreate a new table schema with typed columns.update_custom_tableAdd, change, or drop columns on an existing table.list_secret_keysVault key names only (never values); also polls fulfillment of requested secrets.request_secretAsk the flow's owner to add a credential to the encrypted vault — the human enters the value in Build, so it never passes through the agent.
Extensions
The organization's own extensions plus the public marketplace.
list_extensionsSearchable list of org-owned and public-marketplace extensions.list_extension_surfacesAn extension's embeddable surfaces and their build instructions.list_extension_custom_tablesThe custom tables an org-owned extension registers.install_extensionInstall an extension org-wide, across every company.
Preview, validation & deploy
The same gates Final's own builder uses, plus a live cloud sandbox.
start_previewBoot the server-side preview sandbox; returns a public HTTPS URL.sync_previewReconcile files and run the green-build gate (typecheck + build).get_preview_statusHealth probe plus recent dev-server logs.stop_previewTear the preview sandbox down.validate_flowGuardrails scan, real command-frame typecheck, and secret scan.open_in_builderDeep link into the Build workspace — the recommended way to hand off for deploy.deploy_flowDirect CI-style deploy: gates, sandbox build, then publish to Final web hosting.
Worked examples
Paste any of these into a connected client and watch the flow appear in Build with a live preview.
Bakery counter POS
A complete countertop point of sale, grounded in blueprints and deployed to a real screen.
Build a bakery counter POS: a product grid organized by category (breads, pastries, drinks), a running cart with per-item notes, tap-to-pay checkout, and a receipt with our logo. Start from the closest blueprint, then start a live preview so I can watch.Self-checkout kiosk with a loyalty table
A customer-facing kiosk flow that persists loyalty stamps in an offline-capable custom table.
Create a self-checkout kiosk flow for a cafe. Add a loyalty punch card: create a custom table for customers and stamps, give every 10th drink free, and let customers look themselves up by phone number at checkout. Validate the flow when you're done.Line-busting handheld
A phone-sized flow for taking orders in the queue, handed off to Build for deploy.
Build a mobile line-busting flow for one-handed use on a phone: quick-add buttons for our 12 best sellers, order notes, and Tap to Pay. When it validates green, give me the link to open it in Build so I can deploy it.Frequently asked questions
What is the Final Flows MCP server?
It is a remote MCP (Model Context Protocol) server at build.finalpos.com/api/mcp that lets AI agents — Claude Code, Cursor, ChatGPT, Codex, or any Streamable-HTTP MCP client — build Final POS flows with their own model. Agents get API grounding, screen blueprints, live cloud previews, validation gates, and deploys, and everything they build shows up in the Build workspace.
How do I connect my AI tool?
The fastest path: on build.finalpos.com, start a prompt and choose "Connect your own AI (MCP)" — Build generates a self-contained setup block you paste into your tool. Manual path: mint an organization API key in Build and add the server to your client's MCP config with an Authorization bearer header. ChatGPT and claude.ai connect via OAuth instead of a key.
Is it safe to let an agent build in my account?
Keys are org-scoped, so a connected tool can only touch your own organization's flows. Every file write is a restorable checkpoint, secret values never pass through the agent (humans enter them in Build's masked vault card), write tools are rate-limited, and deploys run the same validation gates as Final's own builder.
Which AI tools can connect?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, and Codex connect with a bearer key; ChatGPT connectors and claude.ai custom connectors use OAuth 2.1. A Gemini CLI extension and a Cursor plugin are also published under Final-Commerce on GitHub.
