Skip to main content
GitHub Copilot supports MCP servers through a mcp.json configuration file in your workspace or user settings. Pointing it at MCPJungle lets Copilot Chat discover and call every tool registered in your gateway. Note that Copilot uses a "servers" key in this file — not "mcpServers" like Claude Desktop.

​
Prerequisites

  • MCPJungle running at http://localhost:8080 (or your deployment URL)
  • GitHub Copilot with MCP support enabled in VS Code or your editor

​
Configure GitHub Copilot

Follow GitHub’s documentation on configuring MCP servers manually to locate or create the mcp.json file for your setup.
1

Open or create mcp.json

Create or edit the mcp.json file in the location specified by GitHub Copilot’s MCP documentation for your editor.
2

Add MCPJungle as a server

Add the following configuration:
{
  "servers": {
    "mcpjungle": {
      "url": "http://localhost:8080/mcp"
    }
  }
}
GitHub Copilot uses the "servers" key, not "mcpServers". Using the wrong key will cause the configuration to be silently ignored.
3

Start the MCPJungle server in Copilot

After saving mcp.json, open Copilot Chat. You may see a Start button next to the MCPJungle entry — click it to establish the connection.
If Copilot does not automatically connect to MCPJungle, look for a Start button in the MCP servers panel and click it manually.
4

Test the connection

In Copilot Chat, ask about available tools to confirm the connection is working:
What MCP tools do you have access to?
Copilot will query MCPJungle and list the tools from all registered servers.

​
Enterprise mode (authentication)

If your MCPJungle instance runs in enterprise mode, create a dedicated MCP client for Copilot and include its access token in the request headers. Create the client with the MCPJungle CLI: 
mcpjungle create mcp-client copilot-local --allow "server1, server2"
Then update mcp.json to send the token: 
{
  "servers": {
    "mcpjungle": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACCESS_TOKEN"
      }
    }
  }
}
Replace YOUR_ACCESS_TOKEN with the token printed by mcpjungle create mcp-client.
In enterprise mode, a client can only access the servers listed in its --allow flag. If Copilot reports no tools, verify the client was created with the correct server names.

​
Limit tools with Tool Groups

If you have many MCP servers registered, use Tool Groups to expose only a relevant subset of tools to Copilot. Create a group and point mcp.json at its dedicated endpoint: 
{
  "servers": {
    "mcpjungle": {
      "url": "http://localhost:8080/v0/groups/copilot-tools/mcp"
    }
  }
}
Run mcpjungle list tools to see all registered tools, then create a group with only the tools your Copilot workflow needs.