Connect your AI

Connect any MCP client

Any AI client that speaks the Model Context Protocol can connect to OpenBudget. One connector URL, one sign-in.

OpenBudget works with any AI that speaks the Model Context Protocol (MCP) — Claude, ChatGPT, Codex, Cursor, and a growing list of others. The setup is always the same: one URL, one sign-in.

How to connect

Connect your bank accounts

Connect banks

Currently available for United States banking institutions.

Add it as a remote MCP server

Two interchangeable ways — use whichever your client supports.

In your client's connector or MCP settings, add a new server using the Streamable HTTPtransport (some clients call it a “custom connector” or “remote MCP server”), name it OpenBudget, and paste the URL below.

https://api.openbudget.sh/mcp

Authorize with OpenBudget

The first time your client calls OpenBudget, it opens your browser to sign in (with the same account you used to connect your banks) and approve read-only access. After that the connection stays active.

Now just ask.

You're all set. Ask your assistant about your spending, subscriptions, or budgets and it'll pull live numbers from OpenBudget.

Your assistant calls OpenBudget automatically — no special prefix needed.

Try asking

Step-by-step guides

Using one of these? We have a tailored walkthrough.

Claude Claude Code ChatGPT Codex Codex CLI Cursor

One endpoint, every client

A standard remote MCP server over Streamable HTTP with OAuth — any spec-compliant client connects. Data is read live.

Read-only by design

Your bank credentials stay with Plaid, never It. The MCP server is read-only — it can't move money or change any account.

Troubleshooting

My AI doesn't see OpenBudget's tools

Make sure the connector is added andenabled, and that you finished the OAuth sign-in. If it still won't use them, ask it directly to “use the OpenBudgetMCP server.” In ChatGPT, start the message with @OpenBudget.

It can't find my transactions

The MCP server only sees accounts you've linked. Open your transactions, confirm your banks are connected and finished their initial sync, then ask again. Make sure you signed in to OpenBudget with the same account you used to link your banks.

The sign-in window didn't open

Authorization happens in your browser. If it didn't open automatically, allow pop-ups and try again, or copy the URL your client shows and open it manually. In Claude Code, run /mcp and choose Authenticate; in the Codex CLI, run codex mcp login openbudget.

It says “needs login” or stopped working

Sign-in tokens can expire. Re-authorize from your client's connector settings, or remove and re-add the OpenBudget server and sign in again — that resolves most connection issues.

Connection failed or the server is unreachable

Confirm the URL is exactly https://api.openbudget.sh/mcp and that you chose the Streamable HTTP transport (not stdio). Make sure your client is up to date — the older SSE transport is deprecated in favor of HTTP.

Still stuck?

Email support@openbudget.sh and we'll help you get connected.

Disclosures

Informational only — not financial advice

OpenBudget surfaces your own financial data, not recommendations. Nothing here is investment, legal, or tax advice — do your own research.

How your data is accessed

OpenBudget connects through Plaid; your bank credentials are never stored by OpenBudget. Data may contain errors or delays and is provided “as is” — verify against your bank.

Read-only access

The OpenBudget MCP server is read-only — it cannot move money, place trades, or modify any account.

Third-party AI clients

Your prompts and the data returned are processed by your AI client (Claude, ChatGPT, Codex, Cursor) under its own terms. AI can be wrong — verify before acting.

Authorization

Connecting grants read access via OAuth; revoke it anytime from your client's settings. Use is governed by our Terms and Privacy Policy.