Connect GitHub Copilot to the Bitsight MCP in VS Code

GitHub Copilot connects to the Bitsight MCP through Agent mode in Visual Studio Code. You add the Bitsight MCP server to an mcp.json file, sign in once, and Copilot can then call Bitsight tools directly from the chat panel.

This article explains how to connect GitHub Copilot in Visual Studio Code to the Bitsight Model Context Protocol (MCP) server.

Before you begin

  • A recent version of Visual Studio Code. MCP support is generally available from version 1.102, and Agent mode is required.
  • The GitHub Copilot extension, installed and signed in with your GitHub account.
  • Bitsight credentials for the products you'll use. See Credentials.
  • GitHub Copilot Business or Enterprise users: Your GitHub organization admin must enable the MCP servers in Copilot policy. It is disabled by default. If the Bitsight server won't start or its tools never appear, check this first.

Choose your authentication method

You need access to Use
Bitsight (SPM, CM, VRM), Bitsight CTI, or both OAuth (recommended)
Bitsight (SPM, CM, VRM) only, and you prefer an API token API token (header)
Bitsight CTI only, and you prefer client credentials CTI Client ID and Client Secret (two headers)
Bitsight and CTI together, and you prefer tokens API token and CTI Client ID and Secret (three headers)

Unlike some other AI clients, VS Code can send multiple custom headers per MCP connection, so every option above works.

OAuth requires no secrets in a configuration file. You choose Bitsight, CTI, or both when you sign in. VS Code supports multiple custom headers for each MCP connection, so all four methods work in this client.

Credentials

  • OAuth: Your normal Bitsight sign-in (and your Bitsight CTI sign-in, if you use CTI). No tokens needed.
  • Bitsight API token: Sign in to service.bitsighttech.com and generate a token under Account Settings > User API Token.
  • Bitsight CTI: Your CTI Client ID and Client Secret.

Instructions

Step 1: Open your MCP configuration

Choose where the Bitsight server should live:

  • Workspace: Create a .vscode/mcp.json file in your project root. The server is available only in that project, and the file can be shared with your team through source control. See Share the setup with your team below.
  • User profile: Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P), run MCP: Open User Configuration, and the server is available in every workspace.

VS Code uses servers as the root key. Other AI clients, such as Claude Desktop, Cursor, and Windsurf, use mcpServers. If you copy a Bitsight snippet written for another client, change mcpServers to servers or VS code will silently load nothing.

Step 2: Add the Bitsight MCP server

The Bitsight MCP is hosted at https://mcp.bitsighttech.com/mcp. Paste one of the configurations below into your mcp.json.

Option A: OAuth (Bitsight, CTI, or both)

{
  "servers": {
    "bitsight-mcp": {
      "type": "http",
      "url": "https://mcp.bitsighttech.com/mcp"
    }
  }
}

Option B: API token (Bitsight SPM, CM, VRM only)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bitsight-api-token",
      "description": "Bitsight API token",
      "password": true
    }
  ],
  "servers": {
    "bitsight-mcp": {
      "type": "http",
      "url": "https://mcp.bitsighttech.com/mcp",
      "headers": {
        "X-Bitsight-API-Token": "${input:bitsight-api-token}"
      }
    }
  }
}

Option C: Bitsight CTI only (client credentials)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "cti-client-id",
      "description": "Bitsight CTI Client ID"
    },
    {
      "type": "promptString",
      "id": "cti-client-secret",
      "description": "Bitsight CTI Client Secret",
      "password": true
    }
  ],
  "servers": {
    "bitsight-mcp": {
      "type": "http",
      "url": "https://mcp.bitsighttech.com/mcp",
      "headers": {
        "X-CTI-Client-ID": "${input:cti-client-id}",
        "X-CTI-Client-Secret": "${input:cti-client-secret}"
      }
    }
  }
}

Option D: Combined (Bitsight SPM, CM, VRM, and CTI) with tokens

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bitsight-api-token",
      "description": "Bitsight API token",
      "password": true
    },
    {
      "type": "promptString",
      "id": "cti-client-id",
      "description": "Bitsight CTI Client ID"
    },
    {
      "type": "promptString",
      "id": "cti-client-secret",
      "description": "Bitsight CTI Client Secret",
      "password": true
    }
  ],
  "servers": {
    "bitsight-mcp": {
      "type": "http",
      "url": "https://mcp.bitsighttech.com/mcp",
      "headers": {
        "X-Bitsight-API-Token": "${input:bitsight-api-token}",
        "X-CTI-Client-ID": "${input:cti-client-id}",
        "X-CTI-Client-Secret": "${input:cti-client-secret}"
      }
    }
  }
}

Theinputs block makes VS Code prompt you for each secret the first time the server starts and store it securely, so you never paste a token into a file that could be committed. Paste the token only, without a "Bearer" prefix.

Step 3: Start the server and sign in

  1. In mcp.json, select Start in the lens above the bitsight-mcp entry. (You can also run MCP: List Servers from the Command Palette, select bitsight-mcp, and choose Start Server.)
  2. Confirm the prompt to trust the server if VS Code asks.
  3. Complete sign-in for the option you chose:
    • OAuth: A browser window opens. Select Bitsight, CTI, or Bitsight+CTI. Sign in to Bitsight (and approve the MCP consent page) or to Bitsight CTI as prompted, then return to VS Code.
    • API token or CTI credentials: Enter the values when VS Code prompts for them.
  4. The entry should show as Running.

Step 4: Switch to Agent mode and review the tools

  1. Open the Copilot Chat panel.
  2. In the chat mode dropdown, select Agent. MCP tools only run in Agent mode. Chat defaults to Ask mode, where the Bitsight tools will not appear.
  3. Select the tools icon in the chat box to see the tools the Bitsight server exposes, and confirm bitsight-mcp  is listed and enabled.
  4. Read-only access: To limit Copilot to reading data, add "X-ReadOnly": "true" under headers for the bitsight-mcp  entry in your mcp.json, and then restart the server. The server then hides all write actions, so the model never sees them. For example, with an API token (Option B):
"headers": {
  "X-Bitsight-API-Token": "${input:bitsight-api-token}",
  "X-ReadOnly": "true"
}
  • If you use OAuth (Option A), add a headers object to the bitsight-mcp  entry that contains only "X-ReadOnly": "true".

  1. The first time Copilot uses a tool, VS Code asks you to confirm. Review the request and choose how broadly to allow it (this call, this session, or always).

Step 5: Test the connection

In Agent mode, ask a test question, for example:

"Using the Bitsight MCP, what is my user info at Bitsight?"

Copilot calls the Bitsight tools and returns your Bitsight user information. From there, try questions about your ratings, portfolio, findings, vendors, or threat intelligence.

Share the setup with your team

To give a whole project the same Bitsight setup, commit .vscode/mcp.json to the repository.

  • Do: Use OAuth (Option A), or the inputs pattern from Options B to D, so each person supplies their own credentials.
  • Don't: Paste an API token, Client ID, or Client Secret directly into a file that is committed.

Each person signs in with their own Bitsight account and sees only the data that account can access.

Other GitHub Copilot clients

The server URL, authentication options, and headers are the same in every GitHub Copilot client. Only the config file location differs. For example, in JetBrains IDEs, select the Copilot icon, and then select Edit settings > MCP > Edit in mcp.json. Use the same servers structure shown above. Agent mode must be enabled in the plugin.

Troubleshooting

Run into a problem? Find your issue below and expand the accordion for troubleshooting tips. If none of them resolve it, contact the Bitsight Support team.

The Bitsight tools don't appear in chat.

Make sure Copilot Chat is in Agent mode, not Ask or Edit. Then confirm the server shows as Running in MCP: List Servers.

Nothing loads and there are no errors.

Check the root key in mcp.json. VS Code requires servers, not mcpServers.

The server won't start, or the option is greyed out (Copilot Business or Enterprise).

Your GitHub organization may not have the MCP servers in Copilot policy enabled. Ask your GitHub admin.

Server stays in "Pending" or shows an error.

Open the Output panel and select MCP from the dropdown to see the exact failure reason. Confirm that https://mcp.bitsighttech.com/mcp is reachable from your network.

Authorization errors or "can't reach the tool".

Your token or session may have expired. 

  • For API token connections, generate a new token in Bitsight (Account Settings > User API Token) and update it: run MCP: List Servers, restart the server, and enter the new value when prompted. 
  • For OAuth connections, sign out of the server's account (Accounts menu in the VS Code activity bar) or remove and re-add the server, then sign in again.
OAuth sign-in fails before reaching the Bitsight login page.

Your organization may restrict third-party sign-in redirects. Contact your Bitsight account team.

CTI questions return no data.

Confirm you selected CTI or Bitsight+CTI during OAuth sign-in, or that the CTI Client ID and Client Secret headers are set (Option C or D).

Copilot answers without using Bitsight data.

Start your question with "Using the Bitsight MCP," or ask Copilot to list the tools it used.

Tools or Agent mode are missing entirely.

Update VS Code and the GitHub Copilot extension to the latest versions.

Publish Date or Recent Edits
  • November 20, 2026: Published.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.