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 without leaving the conversation.
The server acts on your behalf. You sign in with your usual account, and every call is limited to the teams you belong to, following the same role and plan rules as the app. See Tools for what the assistant can do once connected.
The server URL is:
https://mcp.buildnote.io/mcpBefore You Start
A team admin has to allow MCP access before anyone can reach the team's data. In the app, open Settings > General and switch on MCP data access. Only admins see this switch. It applies to the whole team, so once it is on, every member can connect. Until then, the tools that read team data return an error asking you to have an admin enable it.
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. To read files collected during builds, your plan must also collect 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 aren't signed in already). You then see a consent page that names the client asking for access. Select Approve to finish, or Deny to cancel.
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 you don't need to create an API key or paste any credentials. You always authenticate by signing in through your browser.
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 in day-to-day use the assistant reconnects without asking you to sign in again. If you don't use it for 30 days, the client asks you to sign in and approve access again.
Every call checks your team membership at the moment it is made. If you leave a team, the team is deleted, or an admin switches MCP off, the assistant loses access to that team's data straight away, even with tokens issued earlier. Your role's permissions apply just as they do in the app.
To disconnect, remove the connector in your client. Any tokens it held expire on their own.