MCP Server
Buildnote hosts a Model Context Protocol (MCP) server that connects AI assistants such as Claude, Claude Code and Cursor to your team's CI/CD data. Once connected, your assistant can list your teams, write and validate BNQL queries, run them against your collected events, and fetch files collected during builds, all in the middle of a conversation.
The server acts on your behalf. You sign in with your normal account, and every call is limited to the teams you belong to, with the same role and plan rules the app applies. See Tools for what the assistant can do once connected.
The server URL is:
https://mcp.buildnote.io/mcpBefore You Start
Any team member can connect. Running queries follows the same plan rule as the Query page: the team's plan must include API access, which the Pro and Enterprise plans do. Reading files collected during builds needs a plan that collects file events.
Connect From Claude
In claude.ai or the Claude desktop app, open Settings > Connectors, select Add custom connector and paste the server URL. Claude opens a browser window where you sign in to your account (if you are not already signed in) and land on a consent page naming the client that is asking for access. Select Approve to finish, or Deny to abort.
Connect From Claude Code
claude mcp add --transport http buildnote https://mcp.buildnote.io/mcpThen run /mcp inside Claude Code to authenticate. The same sign-in and consent flow opens in your browser.
Connect From Other Clients
Any MCP client that supports the streamable HTTP transport and OAuth authorisation works. Point it at the server URL above. Clients register themselves automatically, so there is no API key to create and no credentials to paste: authentication always goes through your browser sign-in.
How Access Is Authorised
The connection uses OAuth with PKCE. After you approve, the client holds an access token that lasts 8 hours and a refresh token that lasts 30 days, so day to day the assistant reconnects without asking you to sign in again. After 30 days without use, the client sends you through sign-in and consent once more.
Every call checks your team membership at the time of the call. If you leave a team, or the team is deleted, its data stops being accessible immediately, even on tokens issued earlier. Your role's permissions apply in the same way they do in the app.
To disconnect, remove the connector in your client. The tokens it held expire on their own.