MCP server

TuCapi exposes an MCP (Model Context Protocol) server so an AI assistant can look at your account with your own key: the catalog, your balances, any operation by id and its events. Read-only: no tool creates, confirms or cancels operations. Write tools will come behind a dedicated scope and an explicit confirmation.

Connecting

• Over HTTP (ChatGPT, Gemini CLI by URL, any MCP client with the streamable HTTP transport): POST <base URL>/mcp, with your key in Authorization: Bearer <key>. The key travels with every request and determines your company; the server stores no keys.
• Over stdio (Claude Code, Gemini CLI, Codex, on your machine): the mcp binary with the TUCAPI_API_URL and TUCAPI_API_KEY variables. For the sandbox, TUCAPI_API_URL=https://api.tucapi.app/sandbox with a tuc_test_… key.

Tools

Tool	Route	What it returns
balances_list	GET /v2/balances	Your balances per currency
banks_list	GET /v2/banks	The banks of a country
capabilities_get	GET /v2/capabilities	What your key can do today
events_list	GET /v2/events	The events of your operations
methods_list	GET /v2/methods	The method catalog
payins_get	GET /v2/payins/{id}	Look up a pay-in
payouts_get	GET /v2/payouts/{id}	Look up a payout
transactions_get	GET /v2/transactions/{id}	Look up any operation

Each tool returns the same JSON as the matching API route; errors come back as text with the stable code.

Resources

• tucapi://openapi: this contract.
• tucapi://llms.txt: the index of this documentation.
• tucapi://docs/<page>: every page of this documentation, in Markdown.

Ready-made integration packages

• Claude: the tucapi-pagos-v2 Agent Skill (SKILL.md with references) in integraciones/claude/, also as a .zip.
• ChatGPT: the same skill plus the instructions to connect the MCP server in developer mode, in integraciones/chatgpt/.
• Gemini CLI: an extension (gemini-extension.json, GEMINI.md and the skill) in integraciones/gemini/.

All three are generated from this same documentation.