GitHub Copilot

GitHub Copilot supports MCP servers, letting you use Toolcog for API operations alongside Copilot’s code assistance.

Prerequisites

Configuration

Copilot uses VS Code’s MCP configuration. Add Toolcog through any of these methods:

Via Command Palette

  1. Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
  2. Run MCP: Add Server
  3. Select HTTP transport
  4. Enter URL: https://mcp.toolcog.com
  5. Name it toolcog

Via Configuration File

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "toolcog": {
      "type": "http",
      "url": "https://mcp.toolcog.com"
    }
  }
}

Via MCP Registry

GitHub provides a curated MCP Registry. You can add servers from the registry through VS Code’s Extensions view with the @mcp filter.

Using Toolcog with Copilot

In Copilot Chat, ask:

“Find the AWS S3 operations for uploading files”

Copilot will use Toolcog to discover operations, learn their interfaces, and help you use them in your code.

Authentication

When Copilot needs to access your Toolcog account:

  1. Copilot displays an authorization link
  2. Click to sign in to Toolcog in your browser
  3. Return to VS Code

For downstream services (AWS, Stripe, etc.), the same pattern applies.

Organization Policy

If you’re on Copilot Business or Enterprise, your organization admin must enable the “MCP servers in Copilot” policy for MCP servers to work.

Catalogs

Connect to team-specific catalogs:

{
  "servers": {
    "toolcog-team": {
      "type": "http",
      "url": "https://mcp.toolcog.com/mycompany/team-catalog"
    }
  }
}

Verify It’s Working

In Copilot Chat, ask:

“What Twilio operations are available for sending SMS?”

If Copilot returns a list of operations, Toolcog is connected.

Troubleshooting

Server not connecting

Organization restrictions

Authentication errors

Next Steps