Dashboard
Getting started Security & privacy Financial rules for AI agents

Connect Claude.ai to your Monetia account

Monetia exposes a Model Context Protocol (MCP) endpoint so Claude.ai — and any conforming MCP host — can read and write your financial data on your behalf. You stay in control: every connection is scoped to exactly the resources you approve, every call is logged, and you can revoke access at any time.

MCP is an open standard that lets AI assistants call tools on remote services using a structured JSON-RPC protocol. When Claude.ai is connected to Monetia it gains access to tools like get_net_worth, list_accounts, and search_transactions — running them in the cloud under your explicit authorization, not by screen-scraping or password sharing.

1. What is MCP?

MCP (Model Context Protocol) standardizes how AI assistants interact with external services. Instead of the AI guessing at your finances from conversation, it calls well-defined tools with typed parameters and gets structured responses. Monetia implements MCP over HTTPS using OAuth 2.0 with PKCE — the same authorization flow used by "Sign in with Google" buttons — so Claude.ai never sees your Monetia password.

The connection is:

  • Scoped — Claude only sees the resources you explicitly authorize (e.g. read-only accounts, or transactions + reports).
  • Auditable — every tool call is logged and visible in your account activity.
  • Revocable — one click in Settings ends all access immediately.

2. Enable MCP access

MCP access is off by default. You must opt in before any MCP client can connect.

  1. Sign in at https://monetia.carlosmart.dev/.
  2. Go to Settings → AI Assistant access (MCP).
  3. Toggle Enable MCP access ON. A confirmation email is sent to your address.
  4. (Recommended) Enable 2FA at Settings → Security if you have not already done so. Any MCP connection that requests write scopes will require a TOTP verification step during the consent flow.

3. Connect from Claude.ai

Once MCP access is enabled on your account:

  1. In Claude.ai, open Settings → Integrations → Add custom connector.
  2. Enter:
  3. Name: Monetia
  4. Server URL: https://monetia.carlosmart.dev/mcp
  5. Click Connect. Claude.ai fetches the /.well-known/oauth-protected-resource discovery document and learns which authorization server to use — no manual configuration needed.
  6. Your browser opens the Monetia consent screen. You will see:
  7. The name of the client requesting access (Claude.ai).
  8. A checklist of scopes. Read-only scopes are the safe default. Uncheck any resource you do not want Claude.ai to access.
  9. (If 2FA is enabled) Enter your TOTP code or a backup code.
  10. Click Authorize. You are redirected back to Claude.ai with the connection active.

Claude.ai will now list "Monetia" in its connector panel. Access tokens expire after 1 hour; Claude.ai refreshes them automatically in the background.

4. Try a prompt

Once connected, ask Claude.ai natural-language questions about your finances:

"What did I spend on groceries last month?"

"Show me my net worth in USD."

"List my outstanding loans and their remaining balances."

"Which accounts have the highest balance right now?"

Claude.ai will call the appropriate Monetia tools (get_spending_by_category, get_net_worth, list_loans, list_accounts) and summarize the results in plain language.

5. Personal access tokens (advanced)

If you want a long-lived token for scripts, Apple Shortcuts, cron jobs, or other non-Claude integrations, use a Personal Access Token:

  1. Go to Settings → Developer → API Tokens.
  2. Click New token, give it a name, and select the scopes you need.
  3. Copy the token immediately — it is shown only once. The format is mnt_….
  4. Include it in requests as Authorization: Bearer mnt_<token>.

Personal tokens never expire automatically, but you can revoke them at any time. Treat them like a password — do not commit them to version control or share them in chat.

6. Revoke at any time

Three ways to remove access:

Method What it does
Settings → AI Assistant access (MCP) → Connected apps → Revoke (per app) Revokes every access and refresh token of that one app immediately. The app must ask for your consent again to reconnect. Your other connected apps are not affected.
Settings → Developer → API Tokens → Revoke (per token) Invalidates one personal token.
Settings → AI Assistant access (MCP) → turn the switch off Revokes every OAuth token (all connected apps) at once. Personal tokens are not revoked, but they stop working on /mcp while MCP access is off, because MCP access is a hard gate for every token type. Turn it on again and they work again; revoke them from API Tokens to delete them.

Revocation is immediate. Any MCP call using a revoked OAuth token will receive a 401.

The connected-apps list is also available to the mobile app and scripts through GET /api/v1/users/mcp-grants/ and DELETE /api/v1/users/mcp-grants/{client_id}/. An MCP OAuth token cannot call these endpoints, so a connected assistant can never list or remove connections itself.

7. Get help