Skip to content

GitHub Copilot

Connect GitHub Copilot in VS Code to Elaichi once per machine. After that, every app your organization connected in Elaichi, and every tool you are allowed to use, is available in GitHub Copilot Chat. GitHub Copilot is one example of an AI client. Other clients use the same Elaichi endpoint.

Where to find the endpoint: in the Elaichi web app, choose Connect in the sidebar, then copy the endpoint shown in Connect your AI client.

How Elaichi connects to AI clients explains the parts that are the same for every client: one connection, one consent screen and your own access. This page covers only the GitHub Copilot steps in VS Code.

Before you start

Requirement Detail
VS Code A recent version with GitHub Copilot and MCP support.
Where it applies VS Code reads a configuration file, so setup is per machine, and optionally per workspace. Unlike Claude and ChatGPT, there is no account-level setting.
Elaichi account The same sign-in you use for the Elaichi web app.
Your organization's policy If your company manages GitHub Copilot, an administrator can limit which MCP servers you may add.

Connect GitHub Copilot to Elaichi

These steps match VS Code's documentation as of October 2026. Menu names can change.

  1. In VS Code, open the Command Palette and run MCP: Add Server.
  2. Choose HTTP, then paste the endpoint.
  3. Enter elaichi as the server ID.
  4. Choose where to save it. Copilot Global applies to every workspace on this machine. The other destinations are described below.
  5. If VS Code asks you to trust the server, check that it is elaichi, then accept. Then accept its prompt to sign in.
  6. Elaichi's sign-in and consent screen opens in your browser. Pick your organization, choose what the client may do, choose the tools, then select Allow access.

The consent screen shows the name that VS Code registered for itself. Elaichi does not show a verified mark for VS Code, so check that you started this sign-in from VS Code yourself before you allow access.

You will know it worked when you ask GitHub Copilot Chat to use Elaichi and the reply includes an Elaichi tool call. Expand the tool call to see which server ran it.

Where the entry is saved

MCP: Add Server writes one entry with a name, a type and the endpoint. You can also add it by hand. Use the endpoint exactly as Elaichi shows it.

Copilot Global ($COPILOT_HOME/mcp-config.json, or ~/.copilot/mcp-config.json when COPILOT_HOME is not set) and a workspace-root .mcp.json use the portable format:

{
  "mcpServers": {
    "elaichi": {
      "type": "http",
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

A workspace-root .mcp.json is offered in MCP: Add Server only when the experimental chat.mcp.workspaceRootConfig.enabled setting is on.

.vscode/mcp.json in a workspace, and the mcp.json in your VS Code user profile, use the VS Code format. MCP: Add Server labels these destinations as deprecated, but VS Code still reads them:

{
  "servers": {
    "elaichi": {
      "type": "http",
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

If the file already lists other servers, add this entry beside them. Do not replace the block.

Info

Do not add an oauth block, a client ID, a secret or headers. VS Code registers itself with Elaichi by dynamic client registration and signs you in over OAuth.

On the consent screen, for most GitHub Copilot use, keep Read your organization's data and Run your connected tools ticked. Approve what the client can do explains each scope.

Connect your first app

Paste this prompt into GitHub Copilot Chat. It is the same prompt the Connect your AI client dialog gives you. It confirms the connection and helps you connect an app.

Elaichi is connected. List the Elaichi tools you have, then help me connect my first app. If a sign-in comes up, stop and tell me. I approve the access myself.

The last two sentences matter. A model cannot grant itself access to Elaichi, so you must approve each sign-in yourself. Without those sentences, a client can report success while a sign-in waits unanswered.

You connect the app itself in Elaichi, not in VS Code. See Connect an account. Once an app is connected, it appears in GitHub Copilot with no change to the configuration file.

What to know

  • Global or per workspace. Copilot Global applies everywhere on this machine. A workspace file applies to that workspace only. Use a workspace file when only one codebase should reach your tools, and do not commit tokens or secrets to it. The Elaichi entry holds none.
  • Name Elaichi in your question. GitHub Copilot may answer without calling Elaichi. Say "use Elaichi to list my open GitHub issues" so it makes the call.
  • Per machine. Setting up your laptop does not set up your desktop. Repeat the steps, including the sign-in, on each machine.
  • To disconnect, remove the entry from the configuration file, or revoke the grant in Settings → Connected apps in Elaichi. Revoking stops the token working immediately. To clear VS Code's own registration as well, run Authentication: Remove Dynamic Authentication Providers from the Command Palette.
  • If you disconnect an app in Elaichi, it also disappears from GitHub Copilot.

Troubleshooting

Symptom Likely cause
The server does not start Run MCP: List Servers, select elaichi, and choose Show Output to read its log. If you declined the trust prompt, run MCP: Reset Trust and start the server again.
The server never appears after you edit a file by hand The JSON is invalid, or the entry is under the wrong top-level key. .mcp.json and mcp-config.json use mcpServers. .vscode/mcp.json uses servers.
You cannot add the server at all Your organization's GitHub Copilot policy limits MCP servers. Ask your GitHub administrator.
No tools appear after you sign in No app is connected in Elaichi yet, or no toolbox you can reach has tools. Connect an app first.
A tool you expect is missing A restriction blocks it, or it is not in a toolbox you can reach. Connected tools are never listed, so ask GitHub Copilot to search for the tool by name.
A call is refused after consent You did not grant the scope the call needs. Connect again and tick that scope.