Skip to content

Connect via MCP

Munto’s MCP server lets an AI assistant — like Claude or ChatGPT — do nearly everything you can do in the Munto app: read and manage your bills, transactions, accounts, categories, and budgets. You connect and approve one workspace to start; from there the assistant can also work across your other workspaces — but only ones you’re a member of, never anyone else’s.

Every MCP-capable assistant connects to the same URL:

https://mcp.getmunto.app/mcp

Add it as a custom connector in your assistant:

  • Claude (claude.ai) — Settings → Connectors → Add custom connector.
  • ChatGPT — on plans that support custom connectors, add one in ChatGPT’s connector / developer settings.
  • Claude Code, Claude Desktop, Cursor, and other MCP clients — add a remote MCP server pointing at the URL.

However you add it, the flow is the same: you’re sent to sign in to Munto, pick a workspace to connect, and approve. The assistant can then use the tools below in that workspace, and only that workspace.

The exact menu names differ per client and change over time; the constants are the URL above plus the Munto sign-in.

Some clients (like Claude Code or Claude Desktop) want a static credential instead of the sign-in flow. In Munto, go to Settings → Connect to Claude, generate a token (give it a name — it’s shown only once, so copy it before you leave the screen), and pass it as an Authorization: Bearer munto_... header. Revoke it any time from the same screen.

The connector exposes roughly 50 tools — close to full parity with the web and mobile apps. Each tool is annotated as read-only or as a write/destructive action, so your assistant can tell you before it changes anything. By area:

Area What the assistant can do
Bills List (open / paid / all), get one, create, update, mark paid, cancel, delete, merge duplicates; see what you owe in due-date order vs. available cash, committed-by-category rollups, SEPA payment QR, match transactions to a bill, and confirm or dismiss bills auto-detected from your inbox
Transactions List and filter (by account, category, date), create, update, delete, AI-categorize, and import from CSV (deduplicated — safe to re-run)
Accounts List, create, rename, change type, archive / unarchive, delete
Categories List, create, update, and delete categories and category groups
Budget Read a month’s budget (allocated vs. committed vs. spent, with rollover) and set category allocations
More Spending patterns, CSV import templates, merchant lookup, the email-ingest address, showing the connected workspace, submitting feedback, and “who am I”

Every write runs through the same rules and subscription checks as the app. Every action runs in the workspace you connected. The API refuses any other workspace, also one you belong to, and account-level actions such as changing your profile, deleting your account, or creating and revoking API tokens.

Access is OAuth 2.1. You approve one workspace, and the token Claude receives works only in that workspace, not across your whole account. Revoke it any time under Settings → Connected apps. That invalidates the connection immediately.

A static munto_... API token (Claude Code or Claude Desktop, via Authorization: Bearer) is an alternative to the OAuth flow. It has the same limits: it works only in the workspace you created it for. Revoke it under Settings → Connect to Claude.

Claude renews the connection with a refresh token. Each refresh token works once and is replaced by a new one. If an old refresh token is used again, Munto ends the whole connection and you add the connector again.

OAuth connectors approved from claude.ai show up under Settings → Connected apps, where you can see what’s connected and revoke a grant at any time — revoking immediately invalidates the connection. Personal API tokens are managed separately under Settings → Connect to Claude.

A connection covers one workspace. To use the assistant with another workspace, add a second connection and pick that workspace.

  • Stuck in a sign-in / consent loop — clear cookies for getmunto.app and retry the connector setup from Claude; make sure you approve the consent screen rather than closing it.
  • Claude is using the wrong workspace — revoke the connection in Settings → Connected apps, then add the connector again and pick the correct workspace when prompted.
  • Getting a 401 / “invalid or missing token” — the connection was revoked or expired; remove and re-add the connector in Claude.