# rotki MCP server > Open-source, local-first portfolio tracking and accounting app for crypto. Its MCP server, for Premium Basic and higher, lets an AI assistant on the same machine query the user's events and balances with read-only SQL. - Canonical: https://www.anchorterminal.com/tools/rotki-mcp - Markdown: https://www.anchorterminal.com/tools/rotki-mcp.md (~6,900 tokens) - Slim: https://www.anchorterminal.com/tools/rotki-mcp.min.md (~1,430 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/rotki-mcp.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade E · 45.6/100 · rank #865 of 954 · #12 in Accounting & invoicing · not agent-ready · confidence medium** ## Assessment A read-only MCP server in the rotki desktop app, for Premium Basic at €25 a month and above. Privacy modes mask addresses and account names, but amounts, dates, assets and counterparties reach the connected assistant in every mode. The desktop endpoint takes no token, and the feature shipped in v1.44.0 on 21 August 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Rotki Solutions GmbH (https://rotki.com) | | Kind | Platform | | Category | Accounting & invoicing (https://www.anchorterminal.com/categories/accounting) | | Transport | HTTP | | Auth | OAuth or key · Desktop. No credential. The MCP HTTP endpoint at http://127.0.0.1:4445/mcp takes no bearer token, because the desktop launcher forces ROTKI_SESSION_KEY empty outside Docker (https://github.com/rotki/rotki/blob/v1.44.1/crates/starling/src/main.rs). Host and Origin allowlists limit requests to 127.0.0.1:4445. Docker. POST /api/1/mcp/token issues a bearer token scoped to mcp that lasts at most seven days from login and is revoked on logout (https://github.com/rotki/rotki/blob/v1.44.1/docs/dev_changelog.rst; https://docs.rotki.com/usage-guides/mcp). | | Pricing | Paid (Paid) · Premium Basic is €25 a month billed monthly, labelled Suggested, and Advanced is €45 a month billed monthly (https://rotki.com/products/, checked 10 October 2026). Yearly prices are not shown, only 'Save 2 months vs monthly'. The Starter plan and the Supporter plan have no MCP access, and the code excludes Free and Supporter from the tools (https://github.com/rotki/rotki/blob/v1.44.1/rotkehlchen/mcp/premium.py). No free trial was found. | | x402 | No · No x402, MPP or L402 in the docs, the products page or the source (checked 2026-10-10). | | Licence | AGPL-3.0 | | Tools exposed | 8 | | Source | https://github.com/rotki/rotki | | Docs | https://docs.rotki.com/usage-guides/mcp | | llms.txt | https://rotki.com/llms.txt | | Last release | 2026-10-02 | | Vendor | Rotki Solutions GmbH, which operates rotki.com and the Premium subscription (privacy policy, checked 10 October 2026) | | Product | Desktop app (Windows, macOS and Linux per README.md) with a local rotki backend. The MCP server is the Python module rotkehlchen/mcp inside that backend, started from Settings > MCP | | Transport | Streamable HTTP at http://127.0.0.1:4445/mcp on the desktop. Docker serves the same transport at /mcp behind session authentication. The module also accepts stdio (its default), which neither build uses and the docs do not describe | | Tools | Eight. Info (free), list_tables, describe_table, refresh_analytics_data, query_sql, get_asset_details, get_historical_prices, get_event_taxonomy. Seven need Premium Basic or higher | | Privacy modes | balanced (default), strict and raw, set in the desktop app and read from the backend on each tool call. Changing the mode does not need a restart | | Data that leaves the machine | Tool results go to the connected MCP client, which sends them to its model provider. ChatGPT reaches the endpoint through OpenAI's Secure MCP Tunnel. The server itself sends one usage event per session and model to sigil.rotki.com when the analytics setting is on, which is the default | | Premium | Basic €25 a month billed monthly, labelled Suggested; Advanced €45 a month billed monthly. Yearly prices are not shown. No free trial found | | Licence | AGPL-3.0 (LICENSE.md) | | Releases | v1.44.0 on 21 August 2026 introduced the MCP server; v1.44.1 on 2 October 2026 is the latest release | | GitHub | About 4.0k stars and 767 forks on the repository page (rounded there), 389 open issues and 17 open pull requests on 10 October 2026 | | Capabilities | accounting.ledger | | Tags | open-source, self-hosted, local-first, desktop, docker, mcp, read-only, premium, python, llms-txt | | JSON | https://www.anchorterminal.com/api/v1/tools/rotki-mcp.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-10 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 50 | 10.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 76 | 12.3 | | Agent ergonomics | 13% | 16.2 | 69 | 11.2 | | Security & auth | 14% | 17.5 | 20 | 3.5 | | Payments & pricing | 10% | 12.5 | 10 | 1.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 35 | 3.1 | | Transparency & trust (editorial 55, provenance 40) | 7% | 8.8 | 48 | 4.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **45.6 → E** | ### Why each score - Reliability 50: Read with the local-software lines, as localghost was. Installs from the rotki desktop app for Windows, macOS and Linux, as README.md states (https://github.com/rotki/rotki/blob/v1.44.1/README.md), and from a Docker image built from packaging/docker (20). Public CI exists. Rotki_ci.yml runs on pushes to develop and master, and task_backend_tests.yml runs pytest over rotkehlchen/tests, which includes tests/mcp. The Actions page showed no pass or fail for the latest develop run, so passing CI is scored absent (0). Unchecked. GitHub's issue pages are disallowed for our reader, so open crash and regression issues could not be read and score absent (0). The repository page shows 389 open issues and 17 open pull requests on 10 October 2026, without dates or labels. Semver-style releases (1.43.0, 1.43.1, 1.43.2, 1.44.0 and 1.44.1) with breaking changes called out in docs/dev_changelog.rst, for example a renamed message type and a retired environment variable, although MCP tool changes are not listed there (15). Version 1.44.1, past 1.0 (15). Total 50. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 76: The eight tools are registered with FastMCP, and every input is a typed Python parameter, so the JSON Schema served through tools/list is typed on every tool (25). No separate OpenAPI file exists for the MCP server. llms.txt is served at rotki.com/llms.txt, but it indexes the docs and does not mention the MCP tools (10). Descriptions say when to use most tools. Refresh_analytics_data says to call it first, describe_table says to use it before writing SQL, and get_event_taxonomy says to call it before any aggregate over event_type. Use-not-when is implied rather than stated (15 of 20). Inputs are typed but carry no enums or bounds. Tables is a list of free strings with the valid names in the description, max_rows has no schema bound, and time filters accept seconds or milliseconds (6 of 15). get_event_taxonomy carries worked SQLite recipes, and errors come back as structured payloads with a message and an upgrade URL (10 of 15). Versioned releases and a public changelog in docs/changelog.rst and docs/dev_changelog.rst record API changes, but not MCP tool changes (10 of 15). Total 76. - Agent ergonomics 69: Context cost. Eight tools with 9,258 characters of descriptions in total, of which refresh_analytics_data is 2,959 and query_sql 2,667. There is no toolset switch or read-only subset, though the server has no write tools (20 of 25). Output sizing is by row cap, not offset. Query_sql caps results at 500 by default and 5,000 at most, and reports result_truncated and the true row_count. Refresh filters history by time, and --max-events can bound a load, which is off by default. There is no paging cursor (15 of 20). Errors carry a code and a message. Premium_required and premium_check_failed each give an upgrade URL, and SQL errors point to list_tables and describe_table (16 of 20). No readOnlyHint or destructiveHint annotations are set in rotkehlchen/mcp, and every tool is read-only by construction, so retries are safe (10 of 20). Defaults are sensible. Refresh loads history_events unless told otherwise, and few inputs are required. No official SDK for the MCP server or the REST API was found in the repository or the docs we read (8 of 15). Total 69. - Security & auth 20: Credential model, desktop build. None. The launcher forces ROTKI_SESSION_KEY empty outside Docker (https://github.com/rotki/rotki/blob/v1.44.1/crates/starling/src/main.rs), so the server runs without a token, and any local process that can open 127.0.0.1:4445 can call the tools while the server runs (0 of 30). The Host and Origin allowlists in server.py stop browser pages from other origins. Docker takes a bearer token that lasts at most seven days and is revoked on logout, which is a single key and is not scored here. Read-only. No tool writes, and query_sql accepts one SELECT or WITH statement with a denylist, on an in-memory SQLite connection that never writes back to rotki (15 of 20). Prompt injection. Get_asset_details returns token names and symbols from GlobalDB as they are. The code's own comment says an asset name is attacker-controlled on a scam token. No injection guidance was found in the docs (5 of 15). Per-call visibility. The MCP module logs nothing per tool call. The server log follows --log-level, and the usage event goes to rotki when the analytics setting is on (0 of 15). Security programme. No SECURITY.md in the repository, no security.txt, and no bug bounty or disclosure policy found in the sources we read. The GitHub Security tab was not confirmed (0 of 20). Total 20. - Payments & pricing 10: Local software with a paid option, so the rubric scores the Premium plan. No x402, MPP or L402 (0). Plan prices are public without a login. Basic €25 a month and Advanced €45 a month, with no yearly prices shown (10 of 20, plan-only). No free tier reaches the MCP tools. Starter has no MCP access and info is the only free tool (0). A person has to take out a Premium plan and sign in to the desktop app, and no programmatic signup was found (0). Total 10. The free, self-hosted app with nothing to buy would score 20, 20 and 20 on the last three lines, but the MCP tools are paid, so that rule does not apply. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 35: v1.44.1 was released on 2 October 2026, eight days before the check (30). Two releases in the 90 days to 10 October, v1.44.0 on 21 August and v1.44.1 on 2 October, against three needed (0). Responsiveness could not be read, since GitHub's issue pages are disallowed for our reader, so it scores absent (0). No rotki entry was found in the official MCP registry search, and the repository has no server.json (0). Renovate is configured (.github/renovate.json5), dependencies are pinned in uv.lock, and CI is defined, but the latest CI result was not readable (5 of 10). Total 35. - Transparency & trust 48: Source and licence. AGPL-3.0 in LICENSE.md, with the MCP module in the same repository (30). Data handling. The privacy policy at rotki.com/privacy-policy names Rotki Solutions GmbH and covers the website, log data and cookies. It does not mention the desktop app, Premium data or the MCP, and it gives no retention period. The MCP docs say data can be shared with the connected AI client. The statements do not describe what the feature sends, and the app's own strict copy does (10 of 30). Deprecation. No policy for the REST API or the MCP tools was found. The changelog announces renames with 'must migrate' and no notice period (5 of 20). Telemetry. The general settings offer 'Submit anonymous usage analytics', which defaults to on (rotkehlchen/db/settings.py). The MCP server sends a usage event with client name, client version and model to sigil.rotki.com once per session and model. The privacy policy does not describe that event, and it does not name the operator of sigil.rotki.com (10 of 20). Total 55. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/rotki-mcp.md (JSON https://www.anchorterminal.com/fixes/rotki-mcp.json) ### What we couldn't check - unchecked: whether the latest develop CI run passed. The Actions page showed no pass or fail, so passing CI is scored absent and reliability would rise by 25 if it passed. - unchecked: open crash and regression issues, and maintainer responsiveness, because GitHub's issue pages are disallowed for our reader. The MCP issues were not read. - unchecked: any SECURITY policy or disclosure route. The GitHub Security tab was not confirmed, and rotki.com/security.txt and /.well-known/security.txt returned client errors. - unchecked: status.rotki.com, which is disallowed for our reader, and the rotki.com terms of service, which could not be loaded. - unchecked: the domain registration date for rotki.com. The official MCP registry search returned no rotki entry, so a registry listing is not established. - The founder's lead says the server minimises the data shared, and quotes an X post that says 'Share nothing'. We could not read the post. The listing does not repeat that line, and the code sends amounts, dates and counterparties in every mode, so the claim is not made in our copy and no deduction is taken. - The source was read, not run. No command was executed, and the desktop launch, the Docker route and the ChatGPT tunnel were not tested. - The code read is develop at commit 2783d11 (8 October 2026). The MCP files cited are identical at v1.44.1 except for comments and a Windows import shim (_compat.py) that is newer than the release. The launcher and privacy copy cited are from v1.44.1 and unchanged in substance. - The stdio transport exists in rotkehlchen/mcp but is not documented, and the listing records HTTP only. - The repository page rounds the star count to 4.0k, so githubStars is left null. ### Sources - MCP docs page (setup, ports, Docker tokens, privacy wording): (seen 2026-10-10) - products page (Basic and Advanced prices, MCP line): (seen 2026-10-10) - v1.44.0 release (first release with the MCP server, 21 August 2026): (seen 2026-10-10) - v1.44.1 release (latest, 2 October 2026): (seen 2026-10-10) - MCP server entry point and tool registration: (seen 2026-10-10) - MCP tool definitions (eight tools and their docstrings): (seen 2026-10-10) - Premium gate and tier exclusions: (seen 2026-10-10) - Privacy filter, column allowlist and SQL validation: (seen 2026-10-10) - Usage analytics event sent by the MCP server: (seen 2026-10-10) - Default of the usage analytics setting: (seen 2026-10-10) - Desktop launcher and session key handling: (seen 2026-10-10) - Privacy mode copy shown in the app: (seen 2026-10-10) - Docker MCP section and token route: (seen 2026-10-10) - Developer changelog (token endpoint, breaking changes): (seen 2026-10-10) - Privacy policy: (seen 2026-10-10) - llms.txt index: (seen 2026-10-10) - Licence: (seen 2026-10-10) - Repository page (stars, forks, issue and pull request counts): (seen 2026-10-10) ## Who's behind it (provenance 40/100, checked 2026-10-10) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Rotki Solutions GmbH | 20/20 | | Domain age | rotki.com, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | is not on rotki.com | 0/15 | | Terms of service | not found | 0/10 | | Privacy policy | published | 10/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | could not be fetched | 0/10 | The privacy policy names Rotki Solutions GmbH as operator of the website and the Premium API subscription. It states no retention period and no governing law, and does not mention the desktop app or the MCP server. The MCP server runs on the user's own machine, so no vendor endpoint is involved. The only vendor-side request is the optional usage event to sigil.rotki.com. rotki.com/.well-known/security.txt and rotki.com/security.txt both returned client errors to our reader, so securityTxt is recorded as unknown. status.rotki.com and the terms page could not be read by our reader, so statusPage and terms are null. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0. **Privacy policy** (https://rotki.com/privacy-policy), not read yet. ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Read-only by construction. Eight tools and none of them writes, and query_sql accepts one SELECT or WITH statement against an in-memory copy of the loaded data - The premium gate fails closed. Free and Supporter accounts get premium_required, and a backend that cannot be queried gets premium_check_failed - Balanced mode, the default, masks addresses, transaction hashes, group and event identifiers and account names with a per-process seed, and redacts user notes - AGPL-3.0 source for the MCP server, its tests in rotkehlchen/tests/mcp and the desktop launcher that starts it - Typed JSON Schema inputs on every tool, generated from the Python signatures, plus a free info tool that reports whether an unlocked backend is connected ## Weaknesses - The desktop endpoint at http://127.0.0.1:4445/mcp takes no token, because the session key is forced empty outside Docker, so any local process can call it while the server runs - Amounts, USD values, timestamps, asset symbols, counterparties and venue names pass unmasked in every mode, as the in-app strict description says - The privacy policy at rotki.com/privacy-policy does not mention the desktop app or the MCP, and the MCP usage event to sigil.rotki.com is on by default - Two releases in the 90 days to 10 October 2026, and no rotki entry found in the official MCP registry search - The feature is seven weeks old, and no injection guidance, per-call audit log or security disclosure policy was found ## Before you call it (notes for agents) 1. Ask the person to start the server under Settings > MCP in the desktop app, since it stays down until started, then connect to http://127.0.0.1:4445/mcp 2. Call info first. It works without Premium and reports whether an unlocked backend is connected 3. Call get_event_taxonomy before any aggregate over event_type, and sum on direction or event_group, since informational rows double count MEV and block rewards 4. Call refresh_analytics_data before query_sql, and check source.completeness and unpriced_rows before reporting any total 5. Check the privacy mode before answering from the data. Strict keeps amounts and dates, and raw sends addresses, hashes and notes verbatim ## Connect Claude Code: ```bash claude mcp add --scope user --transport http rotki http://127.0.0.1:4445/mcp ``` ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Apideck Accounting API + MCP | BB | 72.9 | 96 | accounting.ledger | no | https://www.anchorterminal.com/tools/apideck-accounting.md | | Merge Accounting API | BB | 70 | 163 | accounting.ledger | no | https://www.anchorterminal.com/tools/merge-accounting.md | | Xero API + MCP | B | 67.2 | 258 | accounting.ledger | no | https://www.anchorterminal.com/tools/xero.md | | Pennylane | B | 66.3 | 298 | accounting.ledger | no | https://www.anchorterminal.com/tools/pennylane.md | | Codat | B | 64.3 | 358 | accounting.ledger | no | https://www.anchorterminal.com/tools/codat.md | | Zoho Books | C | 61.1 | 484 | accounting.ledger | no | https://www.anchorterminal.com/tools/zoho-books.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - v1.44.0, released 21 August 2026, describes 'a local Model Context Protocol server available for premium users' (source: ) - The server exposes eight tools and only info works without Premium. Free and Supporter tiers get premium_required, and an unreadable backend gets premium_check_failed (source: ) - The desktop app starts the server with streamable HTTP on 127.0.0.1:4445 and an empty ROTKI_SESSION_KEY, so no bearer token is required (source: ) - Privacy modes are balanced (default), strict and raw. Strict keeps 'amounts, assets, dates, counterparties, and locations' per the app's own copy (source: ) - A usage event with client name, client version and model goes to https://sigil.rotki.com/api/batch once per session and model when the usage analytics setting is on, which it is by default (source: , ) - The docs say 'MCP can share data from your rotki installation with the AI client you connect' and name only the info tool (source: ) - rotki.com/llms.txt is served and indexes the integrations and comparison pages, but does not mention the MCP server (source: ) - #12 of 13 in Best accounting and invoicing APIs for AI agents: https://www.anchorterminal.com/best/accounting/index.md - All 77 accounting comparisons: https://www.anchorterminal.com/compare/accounting/index.md ## Compare - [Apideck Accounting API + MCP vs rotki MCP server](https://www.anchorterminal.com/compare/apideck-accounting-vs-rotki-mcp.md): BB 72.9 vs E 45.6 - [Codat vs rotki MCP server](https://www.anchorterminal.com/compare/codat-vs-rotki-mcp.md): B 64.3 vs E 45.6 - [FreeAgent API vs rotki MCP server](https://www.anchorterminal.com/compare/freeagent-vs-rotki-mcp.md): C 57.2 vs E 45.6 - [FreshBooks API vs rotki MCP server](https://www.anchorterminal.com/compare/freshbooks-vs-rotki-mcp.md): E 45.4 vs E 45.6 - [Merge Accounting API vs rotki MCP server](https://www.anchorterminal.com/compare/merge-accounting-vs-rotki-mcp.md): BB 70 vs E 45.6 - [Odoo External API vs rotki MCP server](https://www.anchorterminal.com/compare/odoo-vs-rotki-mcp.md): C 55.9 vs E 45.6 - [Pennylane vs rotki MCP server](https://www.anchorterminal.com/compare/pennylane-vs-rotki-mcp.md): B 66.3 vs E 45.6 - [QuickBooks Online API + MCP vs rotki MCP server](https://www.anchorterminal.com/compare/quickbooks-online-vs-rotki-mcp.md): D 49.2 vs E 45.6 - [rotki MCP server vs Rutter Accounting API](https://www.anchorterminal.com/compare/rotki-mcp-vs-rutter.md): E 45.6 vs C 55.6 - [rotki MCP server vs Xero API + MCP](https://www.anchorterminal.com/compare/rotki-mcp-vs-xero.md): E 45.6 vs B 67.2 - [rotki MCP server vs Zoho Books](https://www.anchorterminal.com/compare/rotki-mcp-vs-zoho-books.md): E 45.6 vs C 61.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on rotki.com or one of its subdomains, or the README of github.com/rotki/rotki. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "rotki-mcp", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html rotki MCP server on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![rotki MCP server on Anchor Terminal](https://www.anchorterminal.com/badges/rotki-mcp.svg)](https://www.anchorterminal.com/tools/rotki-mcp) ``` Plain link: ```html rotki MCP server on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say rotki MCP server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/rotki-mcp-dark.png - Light: https://www.anchorterminal.com/assets/share/rotki-mcp-light.png