Rotki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROTKI_MCP_USER | No | Optional: Rotki username for auto-login | |
| ROTKI_MCP_BASE_URL | No | Rotki API base URL | http://127.0.0.1:4242/api/1 |
| ROTKI_MCP_PASSWORD | No | Optional: Rotki password for auto-login | |
| ROTKI_MCP_TIMEOUT_MS | No | HTTP timeout in milliseconds | 120000 |
| ROTKI_MCP_ALLOW_LOGIN_TOOL | No | Enable login tool | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_portfolio_overviewB | Get net worth, allocation, and top positions snapshot. |
| list_transactionsC | List recent transactions within a time window |
| find_transactionsC | Find transactions within a specific time range with optional filters |
| explain_transactionA | Get a human-readable explanation and structured event list for a transaction |
| get_pricesA | Get latest or historical prices for specified assets |
| get_positionsB | Get open positions across exchanges and chains |
| counterparty_summaryB | Get aggregated volume and counts by counterparty |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_portfolio | Guide the model to summarize portfolio risk and allocations |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| user_summary | Portfolio totals, allocation, and recent PnL highlight |
TDQS
Scored across 7 tools
list_transactions and find_transactions are nearly identical in scope, differing only by framing and optional filters, which will cause selection confusion. get_portfolio_overview and get_positions also overlap around positions, so several tools have unclear boundaries.
Most tools follow a get_/list_/find_/explain_ verb_noun pattern, but counterparty_summary is a bare noun and uses a different style. The inconsistency is minor and the naming remains predictable overall.
Seven tools is well within the ideal range and each maps to a meaningful facet of the Rotki domain: overview, transactions, positions, prices, and counterparties. There is no feeling of bloat or excessive fragmentation.
The set covers core portfolio tracking needs: overview, positions, transactions, prices, and counterparty aggregation. Minor gaps exist, such as asset metadata or per-transaction lookup, but these do not seriously block common workflows.