How to Connect T-Bank Business to ChatGPT via MCP

Self-hosted only. T-Bank's T-API presents a TLS certificate issued by the Russian Trusted Root CA, which AnythingMCP Cloud does not trust, so this connector is not available on AnythingMCP Cloud. It works on an AnythingMCP instance you run yourself once that root certificate is added to its trust store, as described below.

T-Bank Business + ChatGPT

T-Bank Business (T-API, formerly Tinkoff Business): company details, accounts and balances, account statements with counterparties, payment confirmations, issued invoice status and card acquiring terminals and operations. Read-only.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

TBANK_API_URL, TBANK_API_TOKEN

Step 1 — Get credentials

Setting up takes about 10 minutes. You need a company account at T-Bank Business and a self-hosted AnythingMCP that trusts the Russian Trusted Root CA (see Certificates below).

1. In T-Business (business.tbank.ru) open Integrations > T-API and click Issue token.
2. Enter the IP addresses the calls come from, or, for small and medium businesses, choose Disable address check. The calls come from the address of your AnythingMCP server, so allow that address or disable the check.
3. Under What the API may access, tick at least company information (T-Business ID), account information (bank-accounts/get) and account operations (statements); add acquiring terminals, invoices and webhooks if you want those tools. You can limit the token to certain accounts.
4. Copy the token into TBANK_API_TOKEN. It stays valid for 90 days after its last use, so a token in regular use does not expire. To change addresses or access, issue a new token.
5. Set TBANK_API_URL to https://business.tbank.ru/openapi. For the sandbox use https://business.tbank.ru/openapi/sandbox with the token TBankSandboxToken; its answers do not depend on your data.
6. Install the connector and run tbank_get_company to check the token.

Certificates: T-API presents a TLS certificate issued by the Russian Ministry of Digital Development (Russian Trusted Root CA); the old public certificates were revoked. A server that does not trust that root fails with a certificate error before any HTTP status. Add the root certificate (from gosuslugi.ru/crt) to the Node trust store of your AnythingMCP backend, for example NODE_EXTRA_CA_CERTS=/path/russian_trusted_root_ca.pem, and restart it.

What it reads: the company behind the token (full and short name, INN, KPP, OGRN, legal form, tax regime, legal address, registration date and bank details); the company accounts with status, type, currency, tariff and balances; account statements from June 2023 with each operation's amount, direction, category, payment purpose and counterparty (name, INN, KPP, account, bank BIC); the bank confirmation of an executed operation as a PDF; the status of invoices issued through T-API; the card acquiring terminals and their card operations; and the configured webhooks.

How the AI works with it: balances come from tbank_list_accounts, where balance.otb is what can be spent now. For a statement it calls tbank_get_statement with account_number and from (and to) and pages with cursor = nextCursor until it is missing; typeOfOperation Credit is money in, Debit money out, and counterparty_inns filters by counterparty. As proof of a payment it fetches tbank_get_payment_document with the operationId and operationDate from the statement, and only when you want the document, because the PDF is large. For card acquiring it lists the terminals with tbank_list_terminals, then calls tbank_list_terminal_operations per terminal and day.

Read-only: all 8 tools only read. No payments are created or signed, so there is nothing to confirm and no tool is switched off at install.

Dates and amounts: date-time parameters and answers are ISO 8601 in UTC; operations on a weekend are booked on the next working day. Amounts are in the account currency (roubles with kopecks as decimals), except acquiring operations, which are in kopecks.

Limits: statements 20 calls per second, accounts and company 6, payment documents and acquiring 1 per second. Statements start in June 2023.

Common errors: 401 means a wrong or expired token, or a call from an address the token does not allow. 403 means the token lacks the access for that method (issue a new token with it ticked) or the account is not allowed for this token. 422 names an invalid parameter, for example an account number that is not 20 digits. Every error has an errorId worth quoting to T-Bank support.

The connector does not make payments, salary registers or self-employed payouts, and does not cover the card methods behind mTLS (secured-openapi) or the partner (OAuth) integration.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

1. Open http://localhost:3000 and register. The first account becomes the admin.
2. Open the connector store (http://localhost:3000/connectors/store), pick T-Bank Business, fill in the credentials it asks for (some connectors need none) and install it.
3. Under MCP Servers, create a server and assign the T-Bank Business connector to it. On the server's page, copy the MCP endpoint (http://localhost:4000/mcp/<server-id>) and generate a key under API keys.

The quickstart listens on localhost only. For an instance that other people or cloud-based AI clients can reach, clone the repository and run ./setup.sh, which sets up a domain, HTTPS and OAuth (deployment guide).

Step 3 — Add the connector in ChatGPT

ChatGPT connects to MCP servers from OpenAI's cloud, so it cannot reach the localhost endpoint of the quickstart. To use T-Bank Business in ChatGPT you need an AnythingMCP instance with a public HTTPS address (see ./setup.sh above) that trusts the Russian Trusted Root CA (see Step 1). Then add the instance's MCP endpoint in ChatGPT under Plugins with Add and Add custom MCP server; OpenAI's guide shows the current steps. Whether you can add one depends on your plan and workspace settings.

If a public instance is not an option, use a client that runs on your computer instead: Claude Code, Cursor or Gemini CLI reach localhost directly.

Available tools

Example prompts

• "What are the balances of all our T-Bank accounts right now, and how much can we spend today?"
• "Show me last week's incoming payments on our main account with counterparty and payment purpose."
• "How much did we pay to the counterparty with INN 7707083893 this quarter?"
• "Get the bank confirmation of yesterday's largest outgoing payment as a PDF."
• "How much did our acquiring terminals take in card payments yesterday?"

FAQ

Does the free ChatGPT plan work with custom MCP servers? OpenAI documents custom MCP servers for paid plans only; the Free plan is not on its list.

Why isn't T-Bank Business available on AnythingMCP Cloud? T-API presents a TLS certificate issued by the Russian Ministry of Digital Development (Russian Trusted Root CA), and AnythingMCP Cloud does not trust that root, so every call would fail with a certificate error. On your own AnythingMCP instance you add the root with NODE_EXTRA_CA_CERTS and restart.

Next steps

• Connector landing page
• Connect to Claude
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot