Connect GitHub Copilot to the Paradime MCP server

First copy your MCP server URL from Step 1 in the Overview.

In your repository (or globally), create or open .vscode/mcp.json.
Add the Paradime entry:

.vscode/mcp.json

{
  "servers": {
    "paradime": {
      "type": "http",
      "url": "<mcp-endpoint-url>"
    }
  }
}

Replace <mcp-endpoint-url> with your MCP server URL.

Reload VS Code and start the server from the mcp.json editor or Copilot Chat. When VS Code asks to authenticate with Paradime, complete the sign-in in the browser and approve the connection.

Connected with a legacy token?

New tokens can’t be generated anymore, but an existing legacy token still works; have VS Code prompt for it:

.vscode/mcp.json

{
  "servers": {
    "paradime": {
      "type": "http",
      "url": "<mcp-endpoint-url>",
      "headers": {
        "Authorization": "Bearer ${input:paradime-token}"
      }
    }
  },
  "inputs": [
    {
      "id": "paradime-token",
      "type": "promptString",
      "description": "Paradime personal access token",
      "password": true
    }
  ]
}

Using ${input:paradime-token} keeps the token out of the file itself; VS Code stores it in its secret store. Don’t commit the file with the token inlined.

Slack Bot Agent

Programmable Agent

Bolt Pipeline Agent

Copilot

MCP Server

Context & Customization

DinoAI Tools

Settings & Credits

Connect GitHub Copilot to the Paradime MCP server

Connected with a legacy token?

​Connected with a legacy token?

Connected with a legacy token?