# Connect with MCP

Discover platform tools and documentation from an AI client.

Updated: 2026-10-02

## Remote connection

```json
{
  "mcpServers": {
    "buildasite": {
      "url": "https://buildasite.ai/api/mcp",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}
```

Configuration syntax differs by client. Use its remote Streamable HTTP option and secret substitution rather than committing a literal token. BuildASite returns JSON responses, uses no server sessions, and has no SSE notification stream. Supported protocol revisions: 2025-03-26, 2025-06-18, and 2025-11-25; initialization negotiates the version.

## Tools share the API contract

tools/list returns only operations allowed by the key's scopes and current role. Tools use the operation names in the API reference. tools/call runs the same validation and database operations as REST. Business errors use isError and a structured error object; protocol errors use JSON-RPC error responses.

resources/list and resources/read expose the public documentation as Markdown. The website_review prompt provides a safe review-and-publish workflow.

## Local stdio adapter

For clients with local MCP subprocess support, download /sdk/mcp-stdio.mjs and run it with Node.js 20 or newer. It forwards newline-delimited JSON-RPC to the remote endpoint. Provide BUILDASITE_API_KEY through your client's secret environment configuration.

```json
{
  "mcpServers": {
    "buildasite": {
      "command": "node",
      "args": ["/absolute/path/mcp-stdio.mjs"],
      "env": { "BUILDASITE_API_KEY": "<your-api-key>" }
    }
  }
}
```

> The adapter is a transport bridge, not a standalone CLI. No OAuth flow, legacy HTTP+SSE transport, or automatic browser-based client installation is included.