Use BugBoard from Codex
You need a BugBoard key and Codex 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
[mcp_servers.bugboard]
url = "https://api.bugboard.ai/mcp/sse"
bearer_token_env_var = "BUGBOARD_MCP_TOKEN"Codex reads MCP servers from the [mcp_servers] tables of ~/.codex/config.toml, or of .codex/config.toml in a project you trust. bearer_token_env_var names the variable whose value Codex sends as the bearer token.
3. Check it
Run codex mcp list. 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
The key is missing, wrong or expired. Check that BUGBOARD_MCP_TOKEN holds a key starting with bb_, and restart Codex so it reads the variable again. The response says whether the key expired or is not valid; an expired key is re-issued on the MCP page.
The key is limited to other projects, or its owner cannot open that project. Projects outside a key's list do not appear at all. Create a key that includes it.
A key can make 300 requests a minute by default. The response says how many seconds to wait. Batch tools such as create_tasks and update_tasks spend one request for up to 100 tasks.
The variable named by bearer_token_env_var must be set in the shell where you start Codex. Export it there and start Codex again.
Config format checked against the Codex documentation on 2026-11-14. Codex MCP documentation This page as Markdown