MCP
Let AI agents find invoices, read documents, and collect invoices from your connected services.
The MCP server runs locally on your device. Only agents running on the same device can connect to it. Keep the Invoice Radar desktop app open while using MCP.
Connect an agent
- Open Invoice Radar, select an organization, and go to Settings → CLI & MCP Access.
- Turn on Enable MCP and expand Connection details.
- Choose Codex, Claude, or Cursor under Setup guide, then follow the instructions shown.
You can also copy the server URL and Authorization header value separately. Keep the header value private.
- Codex desktop / CLI / IDE: Add the shown TOML section to
~/.codex/config.toml, then restart the app or start a new local session. These clients share their configuration. Codex setup guide. - Claude Code: Select Claude and run the shown command with the Claude Code CLI installed. It works across projects in the terminal and local desktop Code tab. Start a new session to connect. Claude Code setup guide.
- Claude Desktop chat: Select Claude and expand Claude Desktop chat setup. Install Node.js, then open Claude's Settings → Developer → Edit Config. Add the
invoice-radarentry from the shown JSON tomcpServersinclaude_desktop_config.json, keeping any other servers. Fully quit and reopen Claude. This uses the third-partymcp-remotebridge. Bridge setup guide. - Cursor: Add the
invoice-radarentry from the shown JSON tomcpServersin~/.cursor/mcp.json, keeping any other servers. If the file does not exist, create it using the full JSON. Restart Cursor. Cursor setup guide.
Other MCP clients can use Streamable HTTP with the local URL and required header shown in Connection details.
Use a client running on this computer. Claude’s cloud connectors cannot reach this local URL, even when added from its desktop app. Claude Desktop’s local configuration is a separate setup.
The server stays connected to the organization where you enabled MCP, even if you switch organizations in the app. It starts again when you reopen Invoice Radar. To change the MCP organization, enable MCP in the other organization's Settings, then update your agent's config with the new connection details.
Check the connection
Ask your agent: “Use Invoice Radar to find my five most recent invoices.”
If it cannot connect, check that Invoice Radar is open, MCP is enabled, and the URL and header match Connection details. Then restart your agent or start a new session.
Available tools
A supported service is something you can connect, such as Stripe. A connected integration is one connection you have added, such as Stripe EU. Use integrations_available to find services and integrations_list to find your connections. Use a supported service’s ID as serviceId when adding a connection. Tools that run or inspect a connection take its integrationId.
| Tool | Purpose |
|---|---|
docs_search | Find documents by vendor, invoice number, amount, date, or extracted PDF text when available. Use offset and limit to page through results. |
docs_show | Read one document's metadata and, with includeText, its extracted PDF text. |
docs_export | Save a PDF to an absolute local path. Use dryRun to check whether export is allowed and whether it requires a credit. |
integrations_available | List supported services you can connect, such as Stripe or Gmail. |
integrations_list | List the connections added to your organization, such as Stripe EU. |
integrations_add, integrations_run, integrations_stop | Add, run, and stop a connected integration. |
debug_continue, debug_state, debug_step_state | Resume a paused run and inspect its state. |
debug_screenshot, debug_get_html, debug_network, debug_run_js | Inspect the integration browser. |
PDF export saves a file on this computer. It can consume a document credit and mark the document exported, following the same export rules as the CLI. Search uses the MCP organization's documents; deleted documents are excluded unless requested.