# Connect BugBoard to Cursor

Once the server is in its config, Cursor can read and write your BugBoard tasks over MCP. You need a BugBoard account and about two minutes.

## 1. Create a token

In BugBoard, open the MCP page and create a key. It starts with bb_ and is shown once. The server keeps only a hash of it, so if you lose it, re-issue it from the same page.

[Open the MCP page](https://bugboard.ai/mcp)

## 2. Put the token in an environment variable

The configs below read the token from BUGBOARD_MCP_TOKEN, so it never lands in a file you commit. Set it in your shell profile or your secrets manager.

## 3. Add the server

Save as .cursor/mcp.json:

```json
{
  "mcpServers": {
    "bugboard": {
      "url": "https://api.bugboard.ai/mcp/sse",
      "headers": {
        "Authorization": "Bearer ${env:BUGBOARD_MCP_TOKEN}"
      }
    }
  }
}
```

.cursor/mcp.json in a project applies to that project. Save it as ~/.cursor/mcp.json to have the server in every project. Cursor resolves ${env:NAME} in headers.

## 4. Check the connection

Ask the agent to list your BugBoard projects: it calls list_projects. Without an agent, this call lists the tools the server offers:

```bash
curl -sS https://api.bugboard.ai/mcp/message \
  -H "Authorization: Bearer $BUGBOARD_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

Authentication is this token. A key can be narrowed to read-only access or to chosen projects, and every call is rate-limited per token; the MCP guide has the details.

- [BugBoard MCP guide (tools, scopes, rate limit), as Markdown](https://bugboard.ai/llms/mcp.md)
- [Cursor MCP documentation](https://cursor.com/docs/context/mcp)
- Config format checked against the Cursor documentation on 2026-11-14.

## Other clients

- [Claude Code](https://bugboard.ai/mcp-server/claude-code.md)
- [VS Code](https://bugboard.ai/mcp-server/vscode.md)
- [Windsurf](https://bugboard.ai/mcp-server/windsurf.md)
- [Codex](https://bugboard.ai/mcp-server/codex.md)
