io.github.Final-Commerce/final-docs — Model Context Protocol (MCP) Server
The MCP server “io.github.Final-Commerce/final-docs” provides search access to the Final POS REST API documentation. Its purpose is to help developers locate relevant information within the Final POS REST API docs by querying the documentation content.
🛠️ Key Features
Searches the Final POS REST API documentation
Server identifier: io.github.Final-Commerce/final-docs
🚀 Use Cases
Finding specific endpoints, fields, or concepts in Final POS REST API documentation
Supporting documentation lookup during development and integration
⚡ Developer Benefits
Enables documentation search via an MCP server
Aligns queries with the Final POS REST API documentation set
⚠️ Limitations
Available behavior is limited to searching the Final POS REST API documentation
Additional capabilities (e.g., tools, parameters, authentication, formats) are not specified in the provided data
API version (required when multiple APIs share the same name but differ by version)
Raw schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "API name",
"minLength": 1
},
"version": {
"type": "string",
"description": "API version (required when multiple APIs share the same name but differ by version)",
"nullable": true
}
},
"required": [
"name"
],
"additionalProperties": false
}
get-full-api-description
Get the complete OpenAPI description
Parameters2
name
string
required
API name
version
string
optional
API version (required when multiple APIs share the same name but differ by version)
Raw schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "API name",
"minLength": 1
},
"version": {
"type": "string",
"description": "API version (required when multiple APIs share the same name but differ by version)",
"nullable": true
}
},
"required": [
"name"
],
"additionalProperties": false
}
search
Search across the documentation to fetch relevant content for a given query
Parameters1
query
string
required
Search query. Should be a single word or that phrase that is presented in a documentation.
Raw schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search query. Should be a single word or that phrase that is presented in a documentation.",
"minLength": 1
}
},
"required": [
"query"
],
"additionalProperties": false
}
Build custom point of sale, kiosk, self-checkout, KDS & in-person payment apps with AI agents —
from Gemini CLI, Claude Code, Cursor, ChatGPT, or any MCP client.
Final lets anyone create their own POS — every pixel,
every permission, every interaction — and run it on any hardware: desktop,
tablet, mobile, kiosk, payment terminal, line buster, or menu board, with
integrated card payments in 24+ countries.
This repo is the official home for connecting your own AI agent to Final.
It ships:
A Gemini CLI extension (this repo installs directly).
The hosted Final Flows MCP server — 20 tools for grounded API lookups,
vetted screen blueprints, flow file writes, live sandbox previews,
validation gates, and deploys.
The Final docs MCP server — search the Final POS REST API.
Setup snippets for Claude Code, Cursor, ChatGPT, and any MCP client.
Everything your agent builds appears live in the Final builder:
the app shows up in your home grid, the agent's session appears as a chat, and
every file write is a restorable checkpoint.
Get an API key
All clients authenticate with a Final organization API key (sk_...):
You'll be prompted for your FINAL_API_KEY during install (stored in your
system keychain). Change it later with:
bash
gemini extensions config final-pos
Then start building:
code
/final-pos:new a coffee-shop kiosk with a product grid, cart, and card payments
/final-pos:preview # live sandbox preview URL
/final-pos:validate # run the full gate suite
/final-pos:deploy # ship it
In ChatGPT, add it as a connector under Settings → Connectors (developer
mode). Works the same in VS Code, Windsurf, Zed, and anything else that speaks
MCP.
A typical build: get_scaffold → create_flow → ground every UI call in
lookup_command_frame → adapt a vetted blueprint → write_flow_files →
validate_flow → start_preview → hand you a live URL.
All tool calls are scoped to your own organization's flows. Rate limits per
key: 30 preview boots/hour, 12 builds+deploys/hour, 300 file writes/hour.
Security
Your API key is org-scoped and revocable; the secret is never stored by
this extension repo — Gemini CLI keeps it in your system keychain.
The MCP servers are hosted by Final; no code from this repo runs locally
except prompt/context files.
Agents cannot touch engine-owned files, and every deploy passes guardrail,
typecheck, and secret scans.
