Read-only financial MCP for AI clients
Bring your financial data into MCP clients without giving up control. Warm MCP runs locally and exposes read-only tools by design.
Local package over stdio · Scoped API keys · No hosted remote MCP endpoint
Available tools
get_accounts · get_transactions · get_financial_state · verify_key
Not exposed
Transfers, edits, deletes, and settings changes.
New to Warm MCP?
Start with the agent workflow narrative — it shows what your AI tools can actually do with Warm context.
MCP setup
Install the local package.
Connect supported clients with one command and a scoped API key from your Warm settings.
Connect supported clients with one command:
npx @warmio/mcpRequires an API key from Settings → API Keys.
Safe by default.
Read-only tools
No write operations
Scoped API keys
Instant revocation
What MCP can access
Exposed via MCP
Accounts, transactions, recurring payments/subscriptions, snapshots, budgets, goals, and financial health.
Not exposed via MCP
Household settings, conversation history, and any write operations such as transfers, edits, or deletes.
FAQ
What does read-only mean for Warm MCP?
Read-only means your AI client can fetch account, transaction, recurring, and snapshot data, but it cannot create, edit, or delete anything.
Can the MCP server move money or change transactions?
No. Warm MCP does not expose any write tools. It cannot transfer funds, edit categories, or update records in your account.
How is access scoped?
Each API key is scoped to the account owner. Your key can access only your financial data and can be revoked instantly from Settings.
Which data is available through read-only MCP?
Accounts, transactions, recurring payments/subscriptions, snapshots, budgets, goals, and financial health are available through read-only MCP tools. Household settings, conversation history, and write operations are not exposed via MCP.
Available on paid Warm plans.