How to Connect MCP Servers to GitHub Copilot

Copilot Now Supports MCP

GitHub Copilot added MCP support in VS Code. Agent mode can call external tools through MCP servers, giving Copilot access to APIs, databases, and internal services beyond its built-in capabilities.

This guide walks through connecting any MCP server (including DataFaucet-generated ones) to Copilot.

Prerequisites

• VS Code with GitHub Copilot extension (v1.200+)
• Copilot Chat enabled (requires Copilot subscription)
• An MCP server URL (SSE endpoint)

Step 1: Open MCP Settings

In VS Code, open your user or workspace settings JSON:

1. Press Ctrl+Shift+P (or Cmd+Shift+P on Mac)
2. Type "Preferences: Open User Settings (JSON)"
3. Add an mcp section if one doesn't exist

Step 2: Add Your Server

Add your MCP server configuration:

{
  "mcp": {
    "servers": {
      "my-analytics": {
        "type": "sse",
        "url": "https://datafaucet.dev/api/mcp/YOUR_SERVER_ID/sse",
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY"
        }
      }
    }
  }
}

Replace YOUR_SERVER_ID and YOUR_API_KEY with values from your DataFaucet dashboard.

Step 3: Verify the Connection

1. Open Copilot Chat (Ctrl+Shift+I)
2. Switch to Agent mode (click the mode selector at the top)
3. Type: "What tools do you have available?"
4. Copilot should list your MCP server's tools

If tools don't appear, check that the URL is reachable and the API key is correct.

Step 4: Use Tools in Conversation

Once connected, reference tools naturally:

• "Pull yesterday's signups from analytics"
• "Check the status of order #4521"
• "What's the current error rate?"

Copilot calls the appropriate MCP tool and returns results inline.

Multiple Servers

Add as many servers as you need:

{
  "mcp": {
    "servers": {
      "analytics": {
        "type": "sse",
        "url": "https://datafaucet.dev/api/mcp/ANALYTICS_ID/sse",
        "headers": { "Authorization": "Bearer KEY_1" }
      },
      "crm": {
        "type": "sse",
        "url": "https://datafaucet.dev/api/mcp/CRM_ID/sse",
        "headers": { "Authorization": "Bearer KEY_2" }
      }
    }
  }
}

Workspace vs User Settings

• User settings: servers available in all projects
• Workspace settings (.vscode/settings.json): servers scoped to one repo, shareable with team (commit the file, use env vars for keys)

For team setups, use workspace settings with a .env reference pattern so keys stay out of git.

Troubleshooting

"No tools available" — Confirm the server URL ends with /sse. Check network connectivity. Try the URL in a browser (should see an SSE stream start).

"Tool call failed" — The MCP server returned an error. Check your DataFaucet dashboard for request logs. Common cause: expired auth tokens that need re-capture.

Slow responses — SSE adds network latency. If you're on a slow connection, responses from tool calls may take 1-3 seconds. This is normal for remote servers.

DataFaucet + Copilot Workflow

1. Browse any web app with DataFaucet (60 seconds)
2. Deploy the generated MCP server (one click)
3. Copy the SSE URL and API key to VS Code settings
4. Ask Copilot questions about that app's data

Total setup time: under 2 minutes from zero to Copilot querying a new API.