Connect GitHub Copilot

GitHub Copilot reaches Wicket two ways: agent mode in your editor, and the Copilot coding agent that works on issues autonomously on github.com. Both call the same Wicket endpoint — and both leave the same audit trail.

Copilot agent mode (in the editor)

Agent mode consumes the editor’s MCP configuration:

• VS Code — native mcp.json; full walkthrough in Connect VS Code
• JetBrains / Eclipse / Xcode — the Copilot plugin manages an mcp.json with the same servers shape; open the Copilot settings → MCP and add:

{
  "servers": {
    "wicket": {
      "type": "http",
      "url": "https://mcp.wicket.sh/mcp",
      "headers": {
        "Authorization": "Bearer <your-member-key>"
      }
    }
  }
}

Copilot coding agent (on github.com)

The coding agent runs in GitHub’s cloud, so the configuration — and the secret — live in your repository settings:

1. In the repo, open Settings → Copilot → Coding agent.
2. Add the member key as a secret named COPILOT_MCP_WICKET_KEY in the copilot environment (Settings → Environments).
3. In the MCP configuration box, add:

{
  "mcpServers": {
    "wicket": {
      "type": "http",
      "url": "https://mcp.wicket.sh/mcp",
      "headers": {
        "Authorization": "Bearer $COPILOT_MCP_WICKET_KEY"
      },
      "tools": ["*"]
    }
  }
}

4. Assign an issue to Copilot as usual — its tool calls now route through Wicket.

Tip

Give the coding agent its own Wicket member (e.g. invite a bot mailbox, approve it, generate its key). The audit log then distinguishes the autonomous agent’s actions from your team’s editor sessions — and you can write stricter policies for it, like read-only outside its assigned repo via repo restrictions.

Verify

Ask Copilot (either surface) to use a connected service — list my GitHub repositories — and watch the call land in the Wicket Audit tab with the right member identity.

Troubleshooting

Symptom	Likely cause
Coding agent: tools never appear	MCP configuration JSON invalid, or secret not in the copilot environment
401 Unauthorized	Secret value wrong or key rotated — update COPILOT_MCP_WICKET_KEY
403 Forbidden	Agent disabled or member not approved
Calls allowed in editor but denied for coding agent	Different member identities hit different policies — check specific_members scopes