T-Invest MCP server with account-id lock
Tinkoff Invest MCP Server
A T-Invest MCP server: portfolio, operations and market data, with a mandatory single-account lock and a sandbox mode
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- It reads the portfolio, balance and operation history of a real investment account
- The API token grants access to account data within its permissions, even though the server does not place orders
Install
Manual install
uv tool install git+https://github.com/akaGelo/tinkoff-invest-mcp.gitInstallation from source via uv tool install.
This is third-party code. Review the repository files before installing.
What it does
The server provides 18 Tinkoff Invest API methods: cash balance, portfolio composition with P&L, operations over a period filtered by status and instrument, candles with a chosen interval, and last prices. For safety, the server requires not just a token but also TINKOFF_ACCOUNT_ID, restricting all operations to one specific account, and TINKOFF_MODE defaults to sandbox instead of the live circuit. MCP Inspector can be connected for debugging.
Who it is for. For individual investors and developers who need agent access to one specific T-Invest account without risking other accounts.
Good fit when
- You need agent access to a T-Invest portfolio, balance and operations
- You need the server hard-limited to one account id for safety
- You need a sandbox mode for testing before the live circuit
Not a fit when
- You need to place buy or sell orders: the README only covers reading the portfolio, operations and market data
- You need to work with several accounts at once in a single server run
Example request
Show my T-Invest portfolio with profit and loss for each positionLimitations
The project has a single author with no known releases and only installs from source via uv tool install. The README describes 18 data-reading methods; nothing is said about placing orders or managing the portfolio. The mandatory TINKOFF_ACCOUNT_ID variable restricts the server to one account; a different account needs a separate run.
How to disable. Remove the server from your MCP client configuration and revoke the T-Invest token if needed.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| TINKOFF_TOKEN required, secret | The T-Invest API token. |
| TINKOFF_ACCOUNT_ID required | The account id all server operations are hard-locked to. |
| TINKOFF_MODE | The mode: sandbox by default or production. |
Security check
- It reads the portfolio, balance and operation history of a real investment account
- The API token grants access to account data within its permissions, even though the server does not place orders
README in short
The Russian README gives the uv tool install-from-source steps, an environment-variable table (TINKOFF_TOKEN, the mandatory TINKOFF_ACCOUNT_ID, TINKOFF_MODE defaulting to sandbox, TINKOFF_APP_NAME), and a section describing the available methods by group: portfolio and balances, operations and history, and market data with candles and intervals.
FAQ
Why is TINKOFF_ACCOUNT_ID mandatory?
The README says this restricts operations to one account for safety reasons.
Can it place orders?
The README does not describe such tools; the server focuses on reading the portfolio, operations and market data.
Related
A set of investment research skills for Claude Code and Codex built on four investors' methodologies. It is a research tool, not investment advice
Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
Alpaca's official MCP server: orders for stocks, ETFs, crypto and options, position management and market data in plain language
inn-check-ru: counterparty risk traffic light
inn-check-ru
An open-source skill that checks a Russian company by tax ID across EGRUL, bailiffs, courts, bankruptcy and sanctions, and returns a dated risk verdict