Skip to main content
GitHub Copilot via MCP lets Corunner query code and repositories with Copilot-quality context. It complements the GitHub Direct Connection for engineering conversations that need deep code intelligence rather than PR signals.

Connect with GitHub Copilot MCP

Open the MCP Servers tab in the Corunner web app.

​
Server details

​
Connect GitHub Copilot MCP

1
Sign in to Corunner at app.corunner.ai.
2
Open Integrations in the left sidebar.
3
Select the MCP Servers tab.
4
Find the GitHub Copilot MCP card in the grid.
5
Turn on the Connect toggle. The Connect GitHub Copilot MCP modal opens.
6
Verify the prefilled Server name (GitHub Copilot MCP by default; rename if you run multiple instances).
7
Verify the prefilled Server URL. Value: https://api.githubcopilot.com/mcp/. The field shows a “Managed by Corunner” hint and is read-only.
8
Click Test URL to confirm the endpoint format is valid and the server responds.
9
Select the authentication method (prefilled OAuth).
10
Click Advanced (Optional) to expand it. This panel contains the Usage guidance field, a free-text instruction that tells agents when and how to use this server. Corunner appends what you enter here to every tool description sent to the agent, so it directly influences when the agent picks GitHub Copilot MCP over another source. Custom headers are hidden for OAuth servers.
11
In the Usage guidance field (placeholder: Tell agents when and how to use this server…), describe when this server should be used, which repositories or actions to prefer, what needs human approval, and what must not be accessed. Keep it short and imperative. Max 2000 characters. See the next section for a copyable example.
12
Click Connect with GitHub Copilot MCP.
13
Corunner redirects the current tab to the provider’s authorization page.
14
Review and approve the requested permissions in the provider consent screen.
15
After approval, return to Corunner automatically.
16
Confirm a green Connected badge and an enabled Connected toggle on the GitHub Copilot MCP card.

​
Configure Usage Guidance

Usage guidance tells Corunner agents when to use GitHub Copilot MCP, what tasks are allowed, which tasks require approval, what must not be accessed, and how to present results. Write it in plain language; agents read it before each interaction with the server.
Never enter secrets, API keys, tokens, or passwords into the Usage guidance field. This field is passed to the model as instruction text and is not a secure vault.

​
Verify the Connection

After you connect, the GitHub Copilot MCP card shows:
  • A green Connected status pill on the name row
  • An enabled Connected toggle
  • A Connected to <workspace> meta line with relative time (exact workspace name and time vary by user)
  • An expandable <N> capabilities button

​
Capabilities

GitHub Copilot MCP exposes the following capabilities to Corunner agents:
  • read repos
  • read issues
  • read code

​
Check Connection Health

On the GitHub Copilot MCP card, click the Test connection icon (Wi-Fi glyph) next to the Connected toggle. This runs a live probe against the server.
  • Green check: the endpoint is reachable and the stored credentials are valid.
  • Red warning: the probe failed.
If the test fails, open Edit configuration to refresh credentials or verify the URL.

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the GitHub Copilot MCP card to open the edit modal. You can change:
  • Server name
  • Server URL (only if not managed by Corunner; read-only for this server)
  • Authentication method and credentials
  • Usage guidance
Creating, editing, and disconnecting MCP servers are admin-only actions. Members see status and capabilities but cannot modify the configuration.
Click the Observation consent icon (brain glyph) on the GitHub Copilot MCP card. Observation is separate from tool connection: it controls whether Corunner passively reads resources into organizational memory, while capabilities available to agents are unaffected. Scopes have:
  • Mode: Disabled, Shadow, or Active
  • Sensitivity: Standard, Restricted, or Excluded
Excluded scopes cannot be enabled. The drawer title is Observation consent - GitHub Copilot MCP.
Observation consent changes are admin-only.
The precise effect on organizational memory of toggling observation off should be confirmed with the Corunner product team if you plan to depend on it in policy. See Memory & Learnings for more details.

​
Disable or Disconnect

Disconnecting deletes stored credentials for this connection. Provider-side OAuth tokens should also be revoked from the provider account if you want to eliminate them entirely.

​
Connect GitHub Copilot MCP

Connect with GitHub Copilot MCP

Ready to go? Open the MCP Servers tab and turn on the GitHub Copilot MCP Connect toggle.

Direct GitHub Connector

Integrations Overview

Agent Roster