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.
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 themcp.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:
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: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:mcp.json to send the token:
YOUR_ACCESS_TOKEN with the token printed by mcpjungle create mcp-client.
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 pointmcp.json at its dedicated endpoint:
