Developer help and AI connections
Connect an AI client to selected Budgee boards or build a controlled Board Tool integration.
Availability is environment-specific. Use only connection and API URLs supplied by Budgee. This help section does not announce a public production endpoint.
Board Tool gives an external AI client or your own integration controlled access to selected Budgee boards. It exposes typed facts, reports, previews, permission checks, and verified changes—not raw database access.
Choose your path
What is available today
The Board Tool implementation includes a Streamable HTTP MCP endpoint, OAuth discovery, dynamic client registration, Budgee sign-in and consent, rotating refresh tokens, a direct HTTP adapter, and read and preview/apply operations.
The standard MCP catalogue currently contains 45 tools. A connection sees only the tools allowed by its granted scopes, mode, and live deployment. Treat the live tools/list response as authoritative.
The intended AI-client connection uses one environment-specific MCP URL ending in /mcp. The direct HTTP API is implemented and secured, but it requires separately provisioned credentials and exact environment URLs, so it does not yet offer the same one-URL onboarding.
What remains
- Confirm which public environment and Board Tool surfaces are enabled.
- Publish the exact customer MCP URL when Budgee has verified it.
- Add client-specific screenshots only after verifying the released ChatGPT, Codex, or other client interface.
- Keep the capability reference aligned with the live
tools/listresponse.
External access and built-in Board AI
External MCP and HTTP access is separate from Ask Budgee AI inside a board. Selecting boards for an external connection does not enable or disable built-in Board AI, and disconnecting an external service is not a master switch for it.