Connect Budgee to an AI client with MCP
Use one Budgee MCP URL to give a compatible AI client controlled access to boards you choose.
Before you begin: obtain the exact MCP URL for your environment from Budgee. Do not infer it from a Budgee web address.
Before you connect
You need a Budgee account with access to at least one board and a compatible remote MCP client. The client must support OAuth-enabled Streamable HTTP MCP.
Connect
- In your AI client's MCP, connector, or tools settings, choose the option to add a remote MCP server.
- Enter the one Budgee MCP URL supplied for your environment.
- Start the connection. The client should discover Budgee's OAuth service and open the Budgee authorization page.
- Sign in using the normal Budgee sign-in flow.
- Review the service name and requested access.
- Select every board you want to share. No board is selected or exposed automatically.
- Check the external-data consent box and approve the connection.
- Return to the client and wait for it to confirm the connection.
Client wording changes over time, so these steps describe the verified protocol rather than unverified ChatGPT- or Codex-specific buttons. A compatible client should not need separate authorization, token, or registration URLs.
Make your first read
Start with a request that proves the board grant and asks for current evidence:
List the Budgee boards I shared with this connection. Then give me the summary of Example Company, including the evidence time and any freshness warning.
A successful client should use budgee.list_boards, then budgee.get_board_summary for the selected board. It should preserve warnings, completeness limits, and freshness status returned by Budgee.
Other useful first questions include:
- “What payments and receipts are coming up in the next 30 days?”
- “Show cash runway for the next 90 days and tell me the lowest point.”
- “Compare actual and forecast totals for last month.”
Prepare and approve a change
Read access does not include write access. The connection must explicitly request the matching write scope and preview:apply, and you must still have a current owner or editor role.
Budgee first returns an immutable preview. Review the exact changes, assumptions, warnings, and impact. Only a later explicit approval can apply that exact preview, and the client must read the affected data back before saying the change succeeded.
Prepare a monthly outgoing forecast of $5,000 for Labour from 1 September 2026. Do not apply it.
After reviewing the preview:
I approve that exact preview. Apply it and verify the result.
A changed or expired preview must be recreated and approved again.
Manage or disconnect the connection
In Budgee, open User settings and find AI connections. Select Disconnect to revoke a connection. Disconnection immediately invalidates its current access and refresh tokens.