Use BugBoard from VS Code
You need a BugBoard key and VS Code installed.
1. Save your key
In BugBoard, open the MCP page and create a key. It starts with bb_ and is shown once. Save it as BUGBOARD_MCP_TOKEN in your shell, not in the repo.
export BUGBOARD_MCP_TOKEN="bb_…"2. Add the server
{
"inputs": [
{
"type": "promptString",
"id": "bugboard-token",
"description": "BugBoard MCP token",
"password": true
}
],
"servers": {
"bugboard": {
"type": "http",
"url": "https://api.bugboard.ai/mcp/sse",
"headers": {
"Authorization": "Bearer ${input:bugboard-token}"
}
}
}
}Portable format: save as .mcp.json
{
"mcpServers": {
"bugboard": {
"type": "http",
"url": "https://api.bugboard.ai/mcp/sse",
"headers": {
"Authorization": "Bearer ${BUGBOARD_MCP_TOKEN}"
}
}
}
}VS Code asks for the key the first time the server starts, so the key is not in the file. If your setup reads the portable .mcp.json in the workspace root instead, use the second file: it has no prompt and reads the key from the environment variable. VS Code's reference says new Copilot configurations should use the destinations MCP: Add Server offers, and describes this servers format for existing setups.
3. Check it
Open the chat in agent mode and look at its tools. bugboard should be listed.
Then ask
- “What bugs are open in my BugBoard project?”
- “File this stack trace as a bug, but check for duplicates first.”
- “Log 45 minutes on the task I just finished.”
Check the key without the editor
This call lists the tools the server offers. It needs only the key, so it tells you whether the key or the editor is the problem.
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"}'If it does not connect
Config format checked against the VS Code documentation on 2026-11-14. VS Code MCP documentation This page as Markdown