For AI agents

The Final MCP server

Updated October 17, 2026 · version 2.0.0

The Final MCP server is the official Model Context Protocol server for Final POS. One remote URL, https://ai.finalpos.com/mcp, lets Claude, ChatGPT, Cursor, VS Code, Gemini CLI, Codex or any MCP client run a merchant's store in Hub — catalog, stock, purchase orders, orders, customers, reports, team, outlets and bookings — and build, preview and deploy point-of-sale apps with Flow. You sign in with your Final account, choose the company and what the agent may do, and there is nothing to install.

It used to be two things: an app-building server for Flow, and the back office you ran by hand. Now it is one server for the whole of Final. The agent works as the person who connected it, on one company, within the packs they allowed, and every call shows up live on your Connections page.

tools

177

packs you choose from

10

URL for Hub and Flow

1

things to install

0

One server for the whole store

Final's AI tools used to be split: an MCP server that only built apps, and a back office your agent couldn't reach. The Final MCP server brings them together behind one sign-in.

How to connect your AI agent to Final

Most clients only need the URL. The whole setup takes about a minute.

1. 1

   Add the server

   Add https://ai.finalpos.com/mcp to your AI tool as a remote MCP server: a custom connector in Claude, an app in ChatGPT's developer mode, or one command in Claude Code, Cursor, VS Code or Gemini CLI.

2. 2

   Sign in with Final

   Your client opens a Final sign-in page. Pick the company and the packs the agent may use, then allow it. Clients without OAuth use a fai_ connection key from ai.finalpos.com/connections instead.

3. 3

   Check the connection

   Ask your agent: "Use Final to tell me which company you're connected to and which packs you can use." It answers with get_connection and list_packs.

4. 4

   Give it real work

   Ask for low stock and a draft purchase order, a sales comparison, a bulk product import, or a new kiosk app with a preview link. Writes are confirmed with you first.

Configuration for each client

Clients with OAuth only need the URL. Codex, scripts and clients without OAuth use a fai_ connection key from ai.finalpos.com/connections; it is shown once, so treat it like a password.

Settings → Connectors → Add custom connector
URL: https://ai.finalpos.com/mcp

Settings → Apps & Connectors → Advanced settings → Developer mode → Create
URL: https://ai.finalpos.com/mcp

claude mcp add --transport http final https://ai.finalpos.com/mcp

{
  "mcpServers": {
    "final": { "url": "https://ai.finalpos.com/mcp" }
  }
}

code --add-mcp '{"name":"final","type":"http","url":"https://ai.finalpos.com/mcp"}'

gemini extensions install https://github.com/Final-Commerce/final-pos-mcp

[mcp_servers.final]
url = "https://ai.finalpos.com/mcp"
http_headers = { "Authorization" = "Bearer fai_YOUR_KEY" }

Remote MCP server (Streamable HTTP): https://ai.finalpos.com/mcp
OAuth 2.1 discovery: https://ai.finalpos.com/.well-known/oauth-protected-resource/mcp

Ask Finai: hand over a whole job

Some jobs are easier to describe than to orchestrate one tool at a time. ask_finai hands a task in plain words to Finai, Final's own AI agent. Finai runs as the connection's user on its company, within the same packs, uses Final's tools itself — looking records up, creating products, building or deploying an app — and returns the finished answer. Pass the conversationId it returns to continue the thread.

Ask Finai to set up a 45-minute massage as a bookable service with two therapists, open 9 to 5 on weekdays, and tell me what it created.

Tools and packs

177 tools, grouped in 10 packs. Packs are also what you allow when you connect. To keep the model's context small a connection lists only a few packs; find_tools searches every allowed pack, call_tool runs any allowed read-only tool and call_write_tool runs any allowed tool that changes data. Every tool has a title and explicit readOnlyHint, destructiveHint and openWorldHint annotations, so clients know which calls to confirm.

The packs

Examples from each pack

All 177 tools, with arguments, on GitHub

Safety, permissions and privacy

• Your role still applies

  Every Hub call runs as the person who connected, and Hub checks their live role on each call.

• Packs are the permission

  The agent can only use the packs you allowed. Change them or disconnect at any time at ai.finalpos.com/connections; disconnecting revokes every token at once.

• Reads and writes are separate

  call_tool only runs tools that read. Anything that creates, changes, deletes, sends or deploys goes through call_write_tool, which clients confirm with you first.

• Money stays on the till

  Taking payments, refunding and voiding orders are not available over MCP. Orders are read-only.

• Secrets never pass through the model

  flow_request_secret asks you to enter an API key in the builder, never in the chat.

• Every call is logged, live

  The Connections page shows each connected client and every call it made as it happens, with a one-line summary of each session.

• Final doesn't see your conversation

  MCP clients send tool calls, not the chat around them. Final keeps the connection, its encrypted token and a redacted log of each call.

Things to ask

Paste any of these into a connected client.

Which products are below their reorder point at the Main Street outlet? Draft a purchase order for the usual supplier and show it to me before you send it.

Compare last week's sales by category with the week before, and tell me which categories moved most.

Add these 40 products from the attached spreadsheet, with photos, and tell me if any are missing a price or category.

Who were my top ten customers this month, and what did they buy?

Build a coffee-shop kiosk with a product grid, modifiers, a cart and card payments. Start from the closest blueprint, validate it, then give me a preview link.

Frequently asked questions

For AI agents: this page is also available as Markdown at finalpos.com/mcp.md.