What comdirect does
The comdirect MCP server exposes read-only access to data held by the comdirect REST API. It covers account and card balances, transactions, depot holdings, securities activity, orders, instrument details, and documents in the comdirect postbox. A typed Python client is also included for scripts that need the same API access without an MCP client.
The available analysis functions can calculate monthly income, expenses, and net cash flow, grouped by counterparty, transaction type, or user-defined category. Other tools identify recurring payments and estimate yearly subscription costs. Portfolio tools report positions and allocation. Transaction handling excludes transfers between the user’s own accounts from spending totals, displays the merchant for PayPal payments, cleans payment text, and masks IBANs.
How the comdirect MCP server works
The server runs over the standard input/output transport using uvx. An MCP client calls the tools, and the server communicates with comdirect’s REST API. Starting a session requires a push TAN approval in the photoTAN app. The login tool begins the session, while logout ends it and revokes the session. The server also stops before comdirect’s lock after five unconfirmed TAN challenges.
Available operations include account, card, and wealth-overview queries; individual transaction retrieval; spending summaries; recurring-payment searches; depot and position queries; portfolio summaries; securities transactions; order and instrument lookups; and postbox document listing and reading. Reading a postbox document marks it as read. The API provides account transactions from the most recent 180 days only.
Setup and configuration
Obtain comdirect API access with a client ID and secret, and use photoTAN Push as the default TAN method. Install uv, then run the configuration command to place credentials in the operating system keychain:
uvx comdirect-mcp@0.6.1 configure
Register the comdirect MCP server with an MCP client. For example, Claude Code can add the stdio server with:
claude mcp add --transport stdio --scope user comdirect -- uvx comdirect-mcp@0.6.1
Claude Desktop and LM Studio can use a configuration containing uvx as the command and comdirect-mcp@0.6.1 as its argument. A Python program can instead instantiate ComdirectClient with the client ID, client secret, username, and password, then call login() and approve the push TAN.
Limitations and notes
The comdirect MCP server is unofficial and is not affiliated with comdirect. It handles banking credentials and financial records, so it should be run only in an environment the operator trusts. Tool results are sent to the model used by the MCP client; with a cloud assistant, financial data can leave the local computer and may appear in logs. A local model is the privacy-oriented option described by the project.
The server is read-only: its tools cannot move money. This does not remove all risk. API changes, compromised dependencies, prompt injection in transaction purposes or documents, and incorrect model interpretation remain possible. Store credentials in the OS keychain, do not commit a plaintext .env file, and review or pin updates before applying them. The project is released under the MIT license.