Appearance

Connect GitHub Copilot to the EdgeComet MCP server ​

You connect GitHub Copilot to EdgeComet by adding https://cloud.edgecomet.com/mcp as an HTTP MCP server in VS Code, Copilot CLI, a JetBrains IDE or Visual Studio. You then sign in to EdgeComet in your browser, and the EdgeComet tools appear in agent mode.

VS Code and Copilot CLI share one personal configuration file, ~/.copilot/mcp-config.json. The steps follow GitHub's and Microsoft's documentation. For the shared steps and revoking access, see Connect an AI client to the EdgeComet MCP server.

Before you start ​

  • An EdgeComet account.
  • GitHub Copilot, signed in.
  • On Copilot Business and Enterprise, the MCP servers in Copilot policy must be on. It is off by default: an organization or enterprise owner turns it on in the Copilot policies. An enterprise allowlist can also limit which servers members can run.

Add EdgeComet in VS Code ​

  1. Open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows and Linux) and run MCP: Add Server.
  2. Choose HTTP (HTTP or Server-Sent Events) and enter https://cloud.edgecomet.com/mcp.
  3. Enter the server ID edgecomet.
  4. Choose Global, then Copilot Global, to use EdgeComet in every project.
  5. On the first connection, VS Code opens your browser on the EdgeComet sign-in screen. Check the account under Signed in as and press Authorize.
  6. Choose Agent in the chat's agent picker. To see the EdgeComet tools, open Chat: Open Customizations > Tools.

You can also start from Chat: Open Customizations > MCP Servers > Add Server.

To share the server with your team, commit a .mcp.json file at the root of the repository. VS Code and Copilot CLI both read it, Copilot CLI after you trust the folder. Each teammate signs in with their own EdgeComet account:

json
{
  "mcpServers": {
    "edgecomet": {
      "type": "http",
      "url": "https://cloud.edgecomet.com/mcp",
      "tools": ["*"]
    }
  }
}

Add EdgeComet to Copilot CLI ​

  1. Run:

    bash
    copilot mcp add --transport http edgecomet https://cloud.edgecomet.com/mcp

    The server is saved to ~/.copilot/mcp-config.json.

  2. Start Copilot CLI and run /mcp. If edgecomet shows needs-auth, run /mcp auth edgecomet and approve the EdgeComet sign-in screen in your browser.

In a session, /mcp add opens the same setup as a form: enter edgecomet as the Server Name, choose HTTP as the Server Type, paste the URL, keep * under Tools and press Ctrl+S.

To edit the file by hand, the entry for Copilot CLI includes the tool list:

json
{
  "mcpServers": {
    "edgecomet": {
      "type": "http",
      "url": "https://cloud.edgecomet.com/mcp",
      "tools": ["*"]
    }
  }
}

Copilot CLI asks before every MCP tool call, read-only tools included. To allow the EdgeComet tools for a session, start it with --allow-tool='edgecomet'.

Add EdgeComet in a JetBrains IDE ​

  1. Press the Copilot icon in the lower right corner and choose Open Chat.

  2. Switch to Agent mode and press the tools icon, Configure your MCP server, at the bottom of the chat.

  3. Press Add MCP Tools. The IDE opens mcp.json.

  4. Add the server and save:

    json
    {
  "servers": {
    "edgecomet": {
      "url": "https://cloud.edgecomet.com/mcp"
    }
  }
}

  5. When the IDE asks you to sign in, approve the EdgeComet sign-in screen in your browser.

Add EdgeComet in Visual Studio ​

  1. In the chat pane, switch to Agent mode from the mode selector at the bottom.
  2. Select Tools to open the tool picker, press the plus (+) button and choose Add custom MCP server.
  3. In the Add MCP server dialog, enter the name edgecomet and the URL https://cloud.edgecomet.com/mcp, and save.
  4. In .mcp.json, select Authentication Required in the CodeLens above the server and approve the EdgeComet sign-in screen.
  5. In the tool picker, turn on the EdgeComet tools you want. Visual Studio adds a server's tools turned off.

Copilot cloud agent on github.com ​

GitHub's docs say: "Copilot cloud agent and Copilot code review do not currently support remote MCP servers that leverage OAuth for authentication and authorization." Use EdgeComet from Copilot in your IDE or in Copilot CLI instead.

Approve EdgeComet tools in Copilot ​

  • VS Code: VS Code's MCP guide says: "VS Code doesn't ask for confirmation to run read-only tools." Your permission mode and tool approval settings can change this. Read-only tools lists the EdgeComet tools marked read-only.
  • Copilot CLI: asks before every MCP tool unless you allow it, such as --allow-tool='edgecomet' for all EdgeComet tools in a session.
  • Visual Studio: asks before it runs a tool, until you allow it.

To use EdgeComet in your repository, add project instructions. See Use EdgeComet MCP with coding agents.

Remove EdgeComet from Copilot ​

  • VS Code: run MCP: List Servers, select edgecomet and choose Uninstall, or delete the entry from the configuration file.
  • Copilot CLI: run copilot mcp remove edgecomet.
  • JetBrains: delete the edgecomet entry from mcp.json.
  • Visual Studio: delete the edgecomet entry from .mcp.json.

Then revoke the connection in EdgeComet. See Manage and revoke connections.

Next ​