01
Connect accounts to Warm
Link checking, credit cards, loans, investments, and other supported accounts so Warm can aggregate everything into one place.
Warm syncs your accounts into one centralized transaction feed. After the sync completes, run npx @warmio/mcp and supported MCP clients can immediately work against the same read-only data.
Workflow
Warm handles the account aggregation and financial normalization once. The AI layer stays lightweight on top.
01
Link checking, credit cards, loans, investments, and other supported accounts so Warm can aggregate everything into one place.
02
After the initial sync finishes, Warm has a centralized, normalized transaction feed ready for analysis.
03
Generate an API key in Warm, then run npx @warmio/mcp to configure supported MCP clients.
04
Use the same read-only feed for prompts, dashboards, agents, and experiments across whichever client you want to try next.
Learn more about how Warm is AI friendly. Learn more →
Why now
Warm is the picks-and-shovels layer: the reusable financial substrate you keep while clients, models, and prompt styles keep moving.
New AI tools show up every week. Warm stays the durable layer below them so your finance context does not have to be rebuilt each time.
Instead of scattered exports, copied spreadsheets, or per-tool reconnect flows, Warm keeps one centralized feed ready for reuse.
Use the same data to ask plain-English questions, generate a dashboard, compare model output, or power an internal agent workflow.
Supported clients
Exposed read-only
Security posture
Warm can expose financial context to AI clients without giving them the ability to move money or edit your accounts.
Your API key only reaches your Warm data, so each MCP client sees your connected accounts and nothing beyond them.
Delete or rotate the key from Warm settings whenever you want to cut off a client or start fresh.
FAQ
Warm handles the hard part once: connecting accounts, syncing transactions, and organizing the data into a centralized financial feed. MCP-compatible AI clients then connect to that shared read-only layer instead of you rebuilding the setup for every new tool.
The supported install flow is "npx @warmio/mcp". It prompts for your Warm API key and configures supported MCP clients automatically.
Warm currently supports Claude Code, Cursor, Codex CLI, Gemini CLI, Windsurf, Claude Desktop, OpenCode, and Antigravity, plus other MCP-compatible clients when configured appropriately.
Warm exposes read-only tools around accounts, transactions, recurring items, snapshots, budgets, goals, health, and key verification. That gives the client enough context to answer questions, compare periods, and build on your financial data.
No. Prompting is the easiest starting point, but the same layer is useful for dashboards, personal agents, code-driven analysis, and experimentation across multiple AI clients.
Yes. MCP and API access are part of Warm Pro, which is the plan intended for AI-ready finance workflows.
Final step
If the opportunity is to sell the picks and shovels for financial AI, Warm should be the durable layer you connect once and keep using everywhere.