June 27, 2026 · 5 minute read
By Nethaven Team · Personal finance research & product team
Connect Nethaven MCP to Claude or ChatGPT
Connect Claude or ChatGPT to Nethaven via MCP in one OAuth step, zero API keys, zero data exports, then ask real questions about your money by chat.
Your money lives in Nethaven, and you want to ask questions about it in a chat. The old way was exporting a CSV, pasting it into an assistant, and hoping nothing sensitive leaked. The new way is one URL and a normal sign-in, after that you can ask Claude, ChatGPT, or Cursor about your real, live finances.
MCP (Model Context Protocol) is the open standard AI assistants use to connect to outside tools, and Nethaven runs an MCP server you connect with a single OAuth sign-in, no API keys involved. In practice that means Claude, ChatGPT, or Cursor can read your live accounts and answer real questions, turning something like a monthly money review into a conversation instead of a spreadsheet session.
What can you ask the assistant about your Nethaven data?
Once connected, the assistant reads your live Nethaven data, not a snapshot or an export, so the answers reflect your accounts right now. The same connection that reads your subscriptions or checking account balance can also make small changes when you ask for them:
- “What’s my net worth right now?”
- “How much did I spend on dining last month?”
- “Which subscriptions have gone up in price?”
- “Log a $42 dinner at Nobu.”
- “Set my grocery budget to $600.”
Because the assistant is reading live data instead of a stale export, a question like "which subscriptions have gone up in price" reflects this month's renewals, not whatever you happened to export weeks ago. That's the actual advantage over the old copy-paste-a-CSV workflow: the answer is never out of date.
What can't the AI assistant do?
This is the part that matters most for a financial app, so it is worth being blunt. The assistant cannot:
- Delete any data
- Link or unlink bank accounts
- Move money
- Make bulk changes
- Access anything outside your own account
Every write action, adding a transaction, changing a category, shows a confirmation step in the assistant before Nethaven does anything. You approve each one individually, the same way you'd approve a payment request rather than let an app move money silently. And you can revoke access any time from Settings → Connect AI assistant, which cuts the connection instantly because nothing was ever copied out.
What actually happens when you connect an assistant?
There is no API key, no script, and no terminal. The assistant signs in as you, just like a mobile app would:
- You paste one URL into your assistant’s settings.
- A login window opens, it is your normal Nethaven sign-in.
- You approve the connection.
- The assistant can now answer financial questions using your real data.
How to connect
- Open your assistant’s connectors or MCP settings.
- Choose “Add custom connector” or “Add MCP server”.
- Paste:
https://api.nethaven.app/mcp - Sign in to Nethaven when prompted.
- Approve individual tool calls before the assistant makes changes.
Where to find the setting in each client:
- Claude: Settings → Connectors → Add custom connector.
- ChatGPT: Settings → Connectors → Add custom connector (where available on your plan).
- Cursor: Settings → MCP → Add new MCP server.
For the full step-by-step with screenshots, see the Connect AI assistant guide or the MCP feature overview.
How is this different from giving an assistant an API key?
Plenty of tools connect to AI assistants through a static API key you generate once and paste into a config file. That key doesn't expire on its own, and if it leaks into a screenshot, a shared repo, or the wrong chat log, whoever has it gets your data until you notice and rotate it. MCP's OAuth sign-in is scoped per assistant instead: Claude, ChatGPT, and Cursor each authenticate separately, none of them holds a long-lived secret, and revoking one leaves the others connected.
This is not a Nethaven convention, it is what the protocol requires. The MCP authorization specification builds on OAuth 2.1 and mandates PKCE on the authorization code flow, Protected Resource Metadata (RFC 9728) for server discovery, and Resource Indicators (RFC 8707) so a token is bound to the specific server it was issued for. That last requirement is the one that matters most in practice: a server must reject a token minted for a different service, which is precisely the failure mode a shared API key invites.
Does connecting an AI assistant require Nethaven Pro?
Yes. The AI assistant connection requires an active Nethaven Pro subscription. See pricing for details.
Track this automatically in Nethaven so accounts, budgets, debt, goals, and subscriptions stay connected between reviews.
Frequently asked questions
Is my financial data sent to the AI company?
Only the answer to what you ask passes through the assistant. When you ask 'What did I spend on dining last month?', the assistant requests that figure from Nethaven and shows it to you. Your full account, like a CSV export, is never uploaded or stored by the AI company.
What if I revoke access, does the AI still have my data?
No. The connection is a live sign-in, not a copy. When you revoke access in Settings → Connect AI assistant, the assistant can no longer read anything new. There is no exported file sitting on its servers because none was ever created.
Which AI assistants are supported?
Any assistant that supports custom connectors or MCP servers, including Claude, ChatGPT, and Cursor. You paste the same Nethaven URL into each one's connector settings and sign in.
Can the assistant make changes without asking me?
No. Every change, adding a transaction, setting a budget, shows a confirmation step in the assistant before Nethaven does anything, and you approve each one individually. The assistant cannot delete data, move money, link bank accounts, or make bulk changes at all.
Do I need a developer account or API key?
No. There is no API key, script, or terminal. You paste one URL and sign in to Nethaven the same way you do in the app. An active Nethaven Pro subscription is required.
Is an OAuth connection actually safer than an API key?
Yes, for two reasons. An OAuth session is scoped to the assistant that created it and can be revoked on its own, while a static API key usually isn't tied to one client and keeps working wherever it was pasted. There's also no long-lived secret sitting in a config file or chat log for a leak to expose.
Can I connect more than one assistant at the same time?
Yes. Claude, ChatGPT, and Cursor each get their own separate connection when you add the MCP URL in their settings. They don't share a session, so approving Claude doesn't automatically approve ChatGPT, and revoking one leaves the others untouched.