Final Flows MCP server
{
"mcpServers": {
"finalpos-final-flows": {
"type": "http",
"url": "https://build.finalpos.com/api/mcp"
}
}
}{
"mcpServers": {
"finalpos-final-flows": {
"type": "http",
"url": "https://build.finalpos.com/api/mcp"
}
}
}{
"mcpServers": {
"finalpos-final-flows": {
"type": "http",
"url": "https://build.finalpos.com/api/mcp"
}
}
}{
"servers": {
"finalpos-final-flows": {
"type": "http",
"url": "https://build.finalpos.com/api/mcp"
}
}
}{
"mcpServers": {
"finalpos-final-flows": {
"type": "http",
"url": "https://build.finalpos.com/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.1
What it does
Final Flows MCP exposes 20 tools for building custom point-of-sale, kiosk, self-checkout, and payment apps using AI agents. Developers can create, preview, validate, and deploy POS applications across desktop, tablet, mobile, and kiosk hardware through integration with Gemini CLI, Claude Code, Cursor, ChatGPT, or any MCP client.
- Build a custom coffee-shop kiosk with product grid, cart, and card payments by having an AI agent scaffold the flow, ground UI calls in vetted blueprints, and deploy it live.
- Create a self-checkout experience by using the agent to look up POS API commands, write flow files, validate the build against guardrails, and preview it in a live sandbox.
- Develop a KDS or payment terminal app by connecting your AI tool to Final, retrieving screen blueprints, iterating through previews, and shipping the app to production with one-click deploys.
Tools this server exposes
| Tool | Does |
|---|---|
| lookup_command_frame | Look up command and UI frame definitions for grounding POS interactions. |
| lookup_pos_api | Search the Final POS REST API documentation. |
| lookup_engine_component | Look up engine component specifications and capabilities. |
| list_blueprints | List available vetted screen blueprints for common POS patterns. |
| get_blueprint | Retrieve a specific vetted screen blueprint. |
| get_scaffold | Generate a project scaffold for a new POS application. |
| list_flows | List all flows in your organization. |
| create_flow | Create a new flow in your organization. |
| connect_chat | Connect a chat session to an existing flow. |
| log_message | Log a message to the flow's chat history. |
| read_flow_files | Read files from a flow. |
| write_flow_files | Write or update files in a flow. |
| delete_flow_files | Delete files from a flow. |
| start_preview | Start a live preview of a flow in a sandbox environment. |
| sync_preview | Sync changes to an active preview. |
| get_preview_status | Check the status of a running preview. |
| stop_preview | Stop a running preview. |
| validate_flow | Run guardrail, typecheck, and secret scan validation on a flow. |
| open_in_builder | Open a flow in the Final builder interface. |
| deploy_flow | Deploy a validated flow to production. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.