Help center
Connect Nethaven MCP to Claude, ChatGPT, or Cursor
How to connect Claude, ChatGPT, or Cursor to Nethaven using the MCP endpoint, no API keys, OAuth sign-in only.
Nethaven works with AI assistants that support remote MCP (Model Context Protocol) connections. You paste one URL into your assistant's settings and sign in, no API keys, no scripts to run. The assistant can then read your financial data and make narrow approved changes by chat. Requires an active Nethaven Pro subscription.
The URL every client needs is the same:
https://api.nethaven.app/mcp. The steps differ only in where each assistant hides that field. Below are the exact click paths for the three clients Nethaven supports today.Claude Desktop, open Settings → Connectors → Add custom connector → choose Remote server → paste
https://api.nethaven.app/mcp → Save → click the new Nethaven connector → sign in to Nethaven in the OAuth window → Approve. On Claude.ai (web), the same option lives under Settings → Connectors.ChatGPT, open Settings → Connectors → Add a new connector → paste
https://api.nethaven.app/mcp → Save → click Connect on the Nethaven card → sign in to Nethaven in the OAuth window → Approve. The connector appears as Nethaven under your installed connectors once it is active.Cursor, open Cursor Settings → MCP → Add new MCP server → choose Remote as the type → paste
https://api.nethaven.app/mcp → Save → click the Nethaven server → sign in to Nethaven in the OAuth window → Approve. The Nethaven tools then appear under the MCP panel and can be enabled per-chat from the chat toolbar.After the OAuth window closes, the assistant shows a green "connected" status next to Nethaven and you can start asking questions right away:
- Reads, net worth, balances, transactions, budget, portfolio, subscriptions run without extra prompts.
- Writes, adding a transaction, changing a category, setting a budget amount, creating a budget show a confirmation step in the assistant that you must approve before Nethaven applies anything.
If your client only supports local stdio config files (no remote-server field), use the
mcp-remote bridge instead, see the FAQ below for the JSON snippet. The endpoint URL and your Nethaven sign-in are identical; only the transport differs.