Install BugMojo in GitHub Copilot
One command in VS Code, plus the API-key path the cloud coding agent needs — because it cannot do a browser login.
VS Code
code --add-mcp '{"name":"bugmojo","type":"http","url":"https://www.bugmojo.com/api/mcp"}'Or add it by hand — this is the same JSON an mcp.json entry uses:
{
"servers": {
"bugmojo": {
"type": "http",
"url": "https://www.bugmojo.com/api/mcp?mode=qa"
}
}
}Add the server with either method above.
Open Copilot Chat and ask about a bug by its key, or ask what to test next.
VS Code prompts for OAuth on the first tool call — complete the browser login.
Check the tool list. If something you expect is missing, call
whoamito see your role and permissions, or reconnect with?mode=all.
The Copilot cloud coding agent
The cloud agent runs without a browser, so the OAuth path is unavailable to it. Give it a BugMojo API key instead.
In BugMojo, open Settings → API keys and create a key. Give it write permission only if the agent should record runs and results.
In your GitHub repository, add it as the secret
COPILOT_MCP_BUGMOJO_TOKEN.Configure the agent's MCP entry to send it as an
Authorization: Bearerheader.Rotate the key when someone leaves, and revoke it in BugMojo the moment it is no longer needed.
Teach the repository
npx @bugmojo/cli init --client copilotinit writes an idempotent managed block into AGENTS.md, CLAUDE.md and .github/copilot-instructions.md, and patches playwright.config.* to add the reporter when one exists. The block is delimited by markers, so re-running it updates in place and leaves the rest of each file untouched.
What Copilot can do once connected
Read a bug with its replay summary, console and network logs; pull an executable repro pack; read the project's test context, plans and environments; propose test cases into the review queue; record a run with evidence; and claim work from the agent inbox — the same queue a Claude Code or Codex session reads, with the same exclusive lease.
Common questions
Why does the cloud agent need an API key?
Copilot's cloud coding agent cannot complete an interactive OAuth flow, so a bearer key is the only way it can authenticate. VS Code itself uses OAuth.
Where do I get the key?
BugMojo → Settings → API keys. Give it write permission if the agent should record runs, and store it as a repository secret, never in a file.
Does Copilot read AGENTS.md?
Yes, and <code>.github/copilot-instructions.md</code> too. <code>bugmojo init</code> writes the same managed block into both.
Why is BugMojo missing from the tool list?
Check the server is listed in <code>.vscode/mcp.json</code>, that you completed the OAuth prompt, and that your role carries the permission the tool needs.
Related articles
- Install BugMojo in Claude CodeInstall the plugin, finish the browser login, and get nine skills, four subagents and three hooks inside your terminal.
- Install BugMojo in ChatGPT and CodexOne plugin package serves both surfaces: add it to Codex from our marketplace, or connect BugMojo in ChatGPT as a connector.
- Install BugMojo in the Gemini CLIInstall the extension, authenticate once, and get the context file, the shared skills and three slash commands.
- Agent access, tokens, and the security modelUnderstand how an AI agent's access is scoped, what it inherits from you, and the guardrails that keep it in bounds.

