# GitHub Copilot MCP connector

The GitHub Copilot connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent manage seats, pull usage reports, and set content exclusions and coding agent policies, with every call running as the signed-in person and logged.

Source: https://elaichi.ai/connectors/githubcopilot/

## Facts

| | |
| --- | --- |
| Application | GitHub Copilot |
| Category | Application Development |
| AI tools | 32 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once GitHub Copilot is connected

- Which GitHub Copilot seats have had no activity in 30 days?
- Add the new platform team hires to GitHub Copilot seats.
- Summarize last week's GitHub Copilot usage report by team.

## Connect GitHub Copilot in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick GitHub Copilot.
2. Optionally set Share with, then press Connect.
3. Paste a GitHub Copilot API key. One person generates a token in GitHub Copilot and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which GitHub Copilot tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## GitHub Copilot MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## GitHub Copilot MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## GitHub Copilot MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## GitHub Copilot MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## GitHub Copilot MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect GitHub Copilot to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a GitHub Copilot tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with GitHub Copilot through Elaichi

### See who is actually using GitHub Copilot

Engineering leadership. Pull the latest enterprise usage report and the per-user report, then ask which seats have gone quiet. Idle seats and the teams that lean on GitHub Copilot the most show up without opening a spreadsheet.

### Put a new hire on a GitHub Copilot seat

IT. Add a person or a whole team to GitHub Copilot seats on their first day, and confirm the seat is live by looking it up by ID. Remove seats in bulk when a contractor engagement ends.

### Reconcile the GitHub Copilot bill each month

Finance. List current billing, compare assigned seats to headcount, and flag the seats to drop before the next cycle. The numbers come from GitHub Copilot itself, not from a forwarded screenshot.

### Keep sensitive repositories out of suggestions

Security. Review the current content exclusions and update them in bulk when a repository is marked confidential. The change is made once and recorded with the name of the person who asked for it.

### Decide which repositories the coding agent can touch

Platform. List the repositories and permissions the GitHub Copilot coding agent has today, update them, or remove a repository it should no longer work in. Permission changes are applied in one pass instead of one setting at a time.

### Roll out coding agent policies across the enterprise

Engineering managers. Create an enterprise coding agent policy, update a set of them together, and delete the ones that no longer apply. Then pull the daily team report to see whether adoption moved after the change.

## Elaichi vs Zapier MCP vs Composio for GitHub Copilot

All three can connect GitHub Copilot to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over GitHub Copilot tools | Allow or restrict single GitHub Copilot tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per GitHub Copilot call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect GitHub Copilot to Claude?

Connect GitHub Copilot in Elaichi by pasting the API key from your GitHub enterprise settings, which is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi as yourself and GitHub Copilot is ready to ask about.

### Does GitHub Copilot work with ChatGPT and Cursor as well as Claude?

Yes. Once GitHub Copilot is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect GitHub Copilot once and every client picks it up.

### What can an AI agent actually do with my GitHub Copilot data?

With GitHub Copilot connected, an agent can look up and assign seats for people and teams, pull the daily and latest usage reports for users, teams and repositories, read billing, and manage content exclusions, coding agent policies, permissions and repositories. Ask things like which seats have been idle for a month or add the new platform hires to seats. Short, concrete asks work better than long paragraphs.

### Does connecting GitHub Copilot give the AI access to my whole enterprise?

No. A GitHub Copilot connection in Elaichi carries only what the key you added is allowed to do, and each person still signs in to Elaichi as themselves, so every call is tied to a named person. Elaichi can narrow that access with roles and restrictions, and it can never widen it beyond what GitHub Copilot already permits.

### Can my team share one GitHub Copilot connection?

Yes. One admin connects GitHub Copilot in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who added a seat or changed a policy, not the admin who connected it.

### Can I stop an agent from deleting or changing things in GitHub Copilot?

Yes. Restrictions in Elaichi work per action on GitHub Copilot, so you can allow reading usage reports while restricting seat removal, repository deletion or policy changes, and set that on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a GitHub Copilot connection when someone leaves?

Offboarding a person in Elaichi ends their access to GitHub Copilot through every client at once. A GitHub Copilot connection that was shared keeps working for everyone else on the team. If you disconnect GitHub Copilot in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the GitHub Copilot MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. GitHub Copilot is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for GitHub Copilot?

Yes. Both let Claude, ChatGPT or Cursor use GitHub Copilot. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every GitHub Copilot call.

### How is Elaichi different from Composio for GitHub Copilot?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to GitHub Copilot: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 32 GitHub Copilot tools

Every tool below is callable through https://api.elaichi.ai/mcp once GitHub Copilot is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single GitHub Copilot seat by ID** (Get). Get Copilot seat assignment details for a single organization member. Returns the seat record including created_at, last_activity_at, plan_type, assignee, and assigning_team. Required: org and id (the member's username handle).
- **List all GitHub Copilot seats** (List). List all Copilot seat assignments for an organization with a Copilot Business or Copilot Enterprise subscription. Returns seat records including created_at, updated_at, last_activity_at, plan_type, and assignee. Required: org.
- **List all GitHub Copilot content exclusions** (List). Get the Copilot content exclusion path rules configured for a GitHub Copilot organization. Returns an object mapping each repository name to its array of excluded paths (e.g. {"octo-repo": ["/src/some-dir/kernel.rs"]}); comments are never returned and only the last occurrence of a duplicate key is kept. Required: org.
- **GitHub Copilot content exclusions bulk update** (Update). Set Copilot content exclusion path rules for an organization, replacing all existing rules. The request body is a map of repository name (or "*" for all repositories) to an array of excluded paths, e.g. {"octo-repo": ["/src/some-dir/kernel.rs"]}. Returns the saved rules in the same shape. Required: org, plus the body map. Comments and duplicate keys are unsupported; 413 if the payload is too large. Requires Copilot Business or Enterprise on the organization. Because the body keys are dynamic repository names, call this through the the connector proxy API rather than as a fixed-parameter tool.
- **GitHub Copilot enterprise coding agent policies bulk delete** (Delete). Remove organizations from the enterprise coding agent policy in GitHub Copilot, disabling Copilot cloud agent for the specified organizations. Targets the organizations either by login or via custom property filters; the enterprise policy must be set to enabled_for_selected_orgs first. Returns an empty 204 response on success. Required: enterprise…
- **Create a GitHub Copilot enterprise coding agent policy** (Create). Add organizations to the enterprise coding agent policy in GitHub Copilot, enabling Copilot cloud agent for the specified organizations by login or custom property filters. The enterprise policy must be set to enabled_for_selected_orgs before using this endpoint. Returns an empty 204 response on success. Required: enterprise (supply organizations…
- **GitHub Copilot enterprise coding agent policies bulk update** (Update). Set the coding agent policy for an enterprise in GitHub Copilot, controlling whether Copilot cloud agent is enabled for all organizations, disabled for all, configured by organization admins, or enabled for selected organizations only. Returns an empty 204 response on success. Required: enterprise and policy_state.
- **List all GitHub Copilot billing** (List). Get Copilot seat information and settings for a GitHub organization, including its subscription's seat breakdown and feature policies. Returns: seat_breakdown, seat_management_setting, ide_chat, platform_chat, cli, public_code_suggestions, plan_type. Required: org. Endpoint is in public preview and subject to change.
- **GitHub Copilot seat teams bulk delete** (Delete). Remove teams from the GitHub Copilot subscription for an organization, revoking Copilot access for all users in each named team. Returns: seats_cancelled. Required: org, selected_teams.
- **Create a GitHub Copilot seat team** (Create). Add teams to the GitHub Copilot subscription for an organization, purchasing a Copilot seat for every user within each specified team. Returns: seats_created. Required: org, selected_teams.
- **GitHub Copilot seat users bulk delete** (Delete). Remove organization members from the GitHub Copilot subscription for an org, revoking their Copilot access and cancelling their seats. Returns: seats_cancelled. Required: org, selected_usernames. Public preview endpoint.
- **Create a GitHub Copilot seat user** (Create). Add organization members to the GitHub Copilot subscription for an org, purchasing and billing a Copilot seat for each listed username. Returns: seats_created. Required: org, selected_usernames. Public preview endpoint.
- **List all GitHub Copilot coding agent permissions** (List). Get the Copilot cloud agent permissions for a GitHub organization — whether the agent is enabled for all, selected, or no repositories. Returns: enabled_repositories, selected_repositories_url. Required: org. This endpoint is in public preview and subject to change.
- **GitHub Copilot coding agent permissions bulk update** (Update). Set the Copilot cloud agent policy for a GitHub organization: whether the agent is enabled for all repositories, selected repositories, or none. Returns an empty 204 response on success. Requires org and enabled_repositories. This endpoint is in public preview and subject to change.
- **GitHub Copilot coding agent repositories bulk update** (Update). Replace the selected repositories enabled for Copilot cloud agent in a GitHub organization with the given list. Returns an empty 204 response on success. Required: org, selected_repository_ids. The coding agent repository policy must be set to selected; the previous selection is replaced wholesale.
- **Delete a GitHub Copilot coding agent repository by ID** (Delete). Disable a repository for Copilot cloud agent in a GitHub organization by removing it from the selected list. Returns an empty 204 response on success. Required: id (repository_id) and org.
- **List all GitHub Copilot coding agent repositories** (List). List repositories enabled for Copilot cloud agent in a GitHub organization when the coding agent repository policy is set to selected. Returns each repository with id, node_id, name, full_name, visibility, and created_at. Required: org.
- **Update a GitHub Copilot coding agent repository by ID** (Update). Enable a repository for Copilot cloud agent in a GitHub organization by adding it to the selected list. Returns an empty 204 response on success. Required: id (repository_id) and org. Only callable when the coding agent repository policy is set to selected.
- **List all GitHub Copilot enterprise repository reports daily** (List). Retrieve download links for a GitHub Copilot enterprise repository report for a specific day, covering per-repository pull request metrics with CCA and CCR breakdowns. Returns: download_links, report_start_day, report_end_day. Required: enterprise, day. Signed URLs expire after a limited time.
- **List all GitHub Copilot enterprise usage reports daily** (List). Get the GitHub Copilot enterprise usage metrics report for a specific day. Returns: download_links, report_day. Required: enterprise, day (YYYY-MM-DD).
- **List all GitHub Copilot enterprise usage reports latest** (List). Get the latest Copilot enterprise usage metrics report for a 28-day period in GitHub. Returns: download_links, report_start_day, report_end_day. Required: enterprise.
- **List all GitHub Copilot enterprise user reports daily** (List). Retrieve download links for the GitHub Copilot enterprise users report for a specific day. Returns: download_links, report_day. Reports are generated daily and cover a complete day of processed usage data. Required: enterprise, day (YYYY-MM-DD).
- **List all GitHub Copilot enterprise user reports latest** (List). Get the latest 28-day Copilot users usage metrics report for an enterprise. Returns download links to NDJSON report files plus the report period. Returns: download_links, report_start_day, report_end_day. Required: enterprise.
- **List all GitHub Copilot enterprise user team reports daily** (List). Get download links for the GitHub Copilot enterprise user-teams report for a specific day, with one entry per user-team pair. Returns: download_links, report_day. Required: enterprise, day. Download URLs are signed and expire after a limited time.
- **List all GitHub Copilot org repository reports daily** (List). Get download links for the GitHub Copilot organization repository report for a specific day. Returns: download_links, report_day. Required: org, day (YYYY-MM-DD). Returns 204 when no report data exists for the day.
- **List all GitHub Copilot org usage reports daily** (List). Get download links for the GitHub Copilot organization usage metrics report for a specific day, with aggregated Copilot feature usage and engagement data in downloadable NDJSON files. Returns: download_links, report_start_day, report_end_day. Required: org, day (YYYY-MM-DD).
- **List all GitHub Copilot org usage reports latest** (List). Get the latest 28-day Copilot usage report for a GitHub organization. Returns: download_links, report_start_day, report_end_day. Required: org.
- **List all GitHub Copilot org user reports daily** (List). Get download links for the GitHub Copilot organization users usage metrics report for a specific day. Required: org, day. Signed URLs have limited expiration; 204 when no data exists for the day.
- **List all GitHub Copilot org user reports latest** (List). Get download links for the latest 28-day GitHub Copilot user usage metrics report for an organization, covering user-level engagement and feature adoption over the trailing 28 days. Returns: download_links, report_start_day, report_end_day. Required: org. Download links are signed and expire after a limited time.
- **List all GitHub Copilot org user team reports daily** (List). Retrieve the GitHub Copilot user-teams report for a specific day for an organization. Returns signed download_links to the report files and the report_day they cover. Required: org, day (YYYY-MM-DD). Responds 204 when no data has been processed for that day.
- **List all GitHub Copilot cloud agent configurations** (List). Get the Copilot cloud agent configuration for a GitHub repository, including MCP server, review tool, workflow approval, and firewall settings. Returns: mcp_configuration, enabled_tools, require_actions_workflow_approval, is_firewall_enabled, custom_allowlist, and 3 more. Required: owner, repo. Public preview; subject to change.
- **List all GitHub Copilot organizations** (List). List the GitHub organizations the authenticated user is a member of. Use the returned login as the org value for every Copilot organization tool (billing, seats, content exclusions, coding agent, usage reports). Returns: login, id, node_id, url, description. Only organizations the token can see are returned (classic PATs need read:org).
