Having trouble with Warm MCP? Start here.
Find the issue below and try the suggested fix. If you're still stuck, we can help.
Find where things stop working.
Pick the problem you see. The diagram shows where Warm stops working and what to try first.
Your AI app
Accounts and transactionsCheck Node.js before installing.
Warm MCP requires Node.js >=18. Run node --version to check yours, and make sure npx works in your terminal. Install your AI app first, then run this command.
Run the Warm installer.
If your key is rejected, check it in Warm.
Open Settings → Export & API. If you deleted the key, create a new one. Run the installer with a valid key, then restart your AI app.
If you set WARM_API_KEY yourself, an old value can override the stored key. Check that setting locally without sharing its value.
If tools are missing, restart your AI app.
Fully quit and reopen it after installation. Then ask it to call get_financial_context.
Still missing? Check your app's MCP status or logs. It needs to find Node.js and npx. Follow the setup guide for your app to check its configuration.
If data is missing, check your connected accounts.
Check your accounts and sync status in Warm. Ask your AI to list the available months with get_financial_context before requesting transactions.
Request a month such as 2026-08 for August 2026. The latest option covers ten days. A missing month means the data isn't available, not that you spent nothing.
If a change fails, check its approval.
The approval_id and input must match the request you approved. If the input changed, you declined, or approval expired, ask your AI to request a new approval with describe_operation.
We can help you get connected.
Contact Warm with your operating system, AI app, Node and Warm MCP versions, and the step that failed. Remove keys, financial details, and approval URLs from any logs or screenshots you share.