Connect to the Bitsight MCP server

Erin Conry

This article details specific steps for how to connect an specific AI client to the Bitsight MCP server and is a part of the Bitsight MCP documentation. Use the table of contents below to jump to the particular instructions you need. For an overview, see Bitsight MCP: Connect Your AI Assistant to Bitsight Data.

Credentials
- Authentication methods
  - OAuth
  - API credentials
Configure your AI client
Web and desktop tools

Credentials

The Bitsight MCP can access one or both of the following product sets:

Bitsight Security Posture Management (SPM), Continuous Monitoring (CM), and Vendor Risk Monitoring (VRM)
Bitsight Threat Intelligence (CTI)

You can connect to the MCP even if you have access to only one of the products.

Each product set uses its own credentials:

Product set	Required credentials
Bitsight (SPM, CM, and/or VRM)	API token
Bitsight Threat Intelligence (CTI)	API client ID and API client secret

You can configure the MCP for either product set individually or for both, depending on the products available to your account.

Authentication methods

You can authenticate with OAuth or with API credentials.

OAuth

If your MCP client supports OAuth and does not allow custom HTTP Authorization headers, enter the MCP server URL and complete the web-based authentication flow when prompted. This method provides access to either product set individually or to both.

API credentials

If your MCP client supports configuring HTTP Authorization headers, API credentials are the recommended authentication method. They provide the most reliable authentication and give access to both Bitsight and CTI through a single MCP connection.

Bitsight API token

The Bitsight API token is required for:

Bitsight (SPM, CM, and/or VRM)
Combined authentication

If you use any of the following products, you need a Bitsight API token associated with your account or demo environment:

Security Posture Management (SPM)
Continuous Monitoring (CM)
Vendor Risk Monitoring (VRM)

To obtain your API token:

Sign in to https://service.bitsighttech.com/.
Click your profile name in the upper-right corner, select Account Settings, and then select User API Token. Alternatively, go directly to https://service.bitsighttech.com/app/account/.
If an API token already exists, copy it.
If no token exists, click Generate.
If you cannot generate a token, contact your Bitsight administrator to enable API access for your account.

CTI API client ID and secret

The CTI API client ID and API client secret are required for:

Bitsight Threat Intelligence (CTI) only
Combined authentication

If you use Bitsight Threat Intelligence (CTI), you need an API client ID and an API client secret.

To generate these credentials:

Go to https://developer.cybersixgill.com.
Click BITSIGHT CTI.
Sign in using your CTI credentials.
Click LOGIN.
Select GENERATE API CLIENT AND SECRET.
Save both the API Client ID and API Client Secret in a secure location. You need them when you configure the MCP or make API requests.

To rotate your credentials later, select GENERATE NEW SECRET. Update any applications that use the previous secret.

If you do not see the GENERATE API CLIENT AND SECRET button and instead see an empty blue notification box, your account may not have API access. Contact your Bitsight administrator or account representative to request API permissions before you generate credentials.

Configure your AI client

Quick start

Choose whether to authenticate with an API token or with OAuth.
Give your AI assistant a link to this article.
Ask, "Can you help me set up the Bitsight MCP using [API token/OAuth]?"

You can also follow the steps in this article yourself.

If the setup fails, ask the assistant, "Why did the setup fail?" Share the error log, your mcp.json file, or both to help the assistant troubleshoot.

CLI tools: simple mcp.json implementation

Generic Bitsight MCP

Most CLI and IDE agents accept a standard MCP configuration file (mcp.json) that contains the MCP URL and optional authentication headers. The Bitsight MCP is hosted at https://mcp.bitsighttech.com/mcp. The Bitsight MCP also supports OAuth-based authentication, which some agents require.

CLI and IDE agents support a global configuration and a per-folder, per-context, or per-project configuration. Configure the Bitsight MCP in a dedicated folder. A dedicated folder keeps the context clean, so other MCP servers, skills, and knowledge don't affect your test, and the Bitsight MCP doesn't affect your other projects.

In a dedicated folder, mcp.json is either directly in the folder or inside a .<appname> folder (note the initial dot), for example .<appname>/mcp.json.

Choose the assistant you use. The setup process is essentially the same across all supported assistants: paste a small JSON configuration snippet into a config file and add your credentials. The process is the same on Mac and Windows.

If your assistant is not listed, the generic implementation likely works. You can also ask your assistant to help configure the MCP by referencing one of the MCP configuration examples in this article for a supported assistant.

If your settings file already exists, it contains entries similar to the following:

{
  "mcpServers": {
      "other-mcp-server": {
      <other-mcp-configuration>
    }
  },
  <remaining-configuration>
}

The mcp.json file is common to all CLI tools. Use the snippet that matches your products.

Bitsight (SPM, CM, and/or VRM) only

{
    "mcpServers": {
        "bitsight-mcp": {
            "url": "https://mcp.bitsighttech.com/mcp",
            "type": "http",
            "headers": {
                "X-Bitsight-API-Token": "<api-token>"
            }
        }
    }
}

Bitsight CTI only

{
    "mcpServers": {
        "bitsight-mcp": {
            "url": "https://mcp.bitsighttech.com/mcp",
            "type": "http",
            "headers": {
                "X-CTI-Client-ID": "<your-cti-client-id>",
                "X-CTI-Client-Secret": "<your-cti-client-secret>"
            }
        }
    }
}

Combined (Bitsight SPM, CM, VRM, and CTI)

{
    "mcpServers": {
        "bitsight-mcp": {
            "url": "https://mcp.bitsighttech.com/mcp",
            "type": "http",
            "headers": {
                "X-Bitsight-API-Token": "<your-api-token>",
                "X-CTI-Client-ID": "<your-cti-client-id>",
                "X-CTI-Client-Secret": "<your-cti-client-secret>"
            }
        }
    }
}

OAuth for Bitsight, CTI, or both

Use this mcp.json configuration to authenticate with OAuth for Bitsight, CTI, or both:

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

Then complete the OAuth flow:

Click Authenticate in your client.
In the browser page that opens, select Bitsight, CTI, or Bitsight+CTI.
If you selected Bitsight or Bitsight+CTI:
- If you are not yet authenticated, your browser goes to the Bitsight login page.
- Your browser then goes to an MCP consent page.
If you selected CTI or Bitsight+CTI, and you are not yet authenticated, your browser goes to the CTI login page.

Get the Bitsight connector from the Claude directory

Go to claude.ai/directory/bitsight and click Connect (or Add) on the Bitsight listing. You can also search the Claude directory for Bitsight.
If Claude asks you to confirm the connector, review the permissions and approve.
You’ll be redirected to Bitsight’s sign-in page. Sign in with your Bitsight account and approve access. Claude doesn’t see your password.
When you’re returned to Claude, the connector should show as connected. You can check under Customize > Connectors (or Settings > Connectors).
To test it, ask something read-only, such as “What MCP tools do you have from Bitsight?” or “Show me my portfolio’s current ratings.”

Claude Desktop (Code)

Select Code in the upper-left corner.
Start a new session and select a new, empty folder.
In that folder, create a file named .mcp.json (note the initial dot). Use the contents of the mcp.json snippet that matches your products from Generic Bitsight MCP, and replace the placeholders with your credentials.
Ask Claude a question such as "Using the Bitsight MCP, what is my user info at Bitsight?"

The Claude Desktop app in Code mode automatically loads and reads the MCP configuration. If it does not, restart the app and create a new session.

Claude Desktop in Code mode answering a question through the Bitsight MCP

Claude Code (CLI)

To configure the Bitsight MCP for Claude Code, use either of the following methods:

Create a file named .mcp.json (note the initial dot) in an empty folder. Use the contents of the mcp.json snippet that matches your products from Generic Bitsight MCP, and replace the placeholders with your credentials.
Use the claude mcp … command to let Claude manage the MCP configuration file.

To register bitsight-mcp in the project-scoped configuration with the claude mcp command, run one of the following commands. Replace the placeholders with your real credentials.

Combined (Bitsight SPM, CM, VRM, and CTI)

claude mcp add --scope project bitsight-mcp --transport http \
  https://mcp.bitsighttech.com/mcp \
  --header "X-Bitsight-API-Token: <your-api-token>" \
  --header "X-CTI-Client-ID: <your-cti-client-id>" \
  --header "X-CTI-Client-Secret: <your-cti-client-secret>"

Bitsight (SPM, CM, and/or VRM) only

claude mcp add --scope project bitsight-mcp --transport http \
  https://mcp.bitsighttech.com/mcp \
  --header "X-Bitsight-API-Token: <api-token>"

CTI only

claude mcp add --scope project bitsight-mcp --transport http \
  https://mcp.bitsighttech.com/mcp \
  --header "X-CTI-Client-ID: <your-cti-client-id>" \
  --header "X-CTI-Client-Secret: <your-cti-client-secret>"

These commands write to .mcp.json in the project root. The configuration is project-scoped, not user-global.

To make the MCP global, set the --scope flag to user. Without the flag, the scope defaults to project, and the MCP works only in that project.

To remove an MCP, or to remove and re-add it to switch MCPs, run:

claude mcp remove <mcp-name>

VSCode, Cursor, Kiro (IDE)

Open or create the MCP configuration file for your IDE:
- VSCode: ~/.vscode/mcp.json
- Cursor: ~/.cursor/mcp.json
- Kiro: ~/.kiro/settings/mcp.json
Paste the mcp.json snippet that matches your products from Generic Bitsight MCP into the file, and replace the placeholders with your real credentials.
If the file has no HTTP Authorization headers, the IDE asks to open the browser to authenticate.
- To use API credentials, cancel the pop-up and add the headers to the file.
- To use OAuth, continue with the web authentication flow.
Confirm that bitsight-mcp appears under Installed MCP Servers, listed as connected with tools enabled.

Each IDE has its own MCP menus that can help you configure the JSON file or find where the file is located:

VSCode: Press Cmd-Shift-P (or Ctrl-Shift-P) to open Show and run commands, select MCP: Add server, select HTTP, and enter the MCP URL and name.
Cursor: Select the Cursor menu, select Cursor Settings, select Tools & MCPs, and then select New MCP Server.

Web and desktop tools

Claude Desktop (Chat and Cowork)

Select Chat (or Cowork) in the upper-left corner.
Select Customize in the left menu.
Select Connectors in the updated left menu.
In the Connectors view, click the + icon. A pop-up with Add custom connector should appear.
- If this option is not available, use the workaround in Claude Desktop (Chat and Cowork) without the custom connector option.
- Free accounts can add only a single custom connector.
- Enterprise accounts may have this option disabled by IT.
In the custom connector view, enter the following values:
- Name: bitsight-mcp
- URL: https://mcp.bitsighttech.com/mcp
Click Authenticate.

Claude Desktop (Chat and Cowork) without the custom connector option

Use this configuration when Add custom connector is not available in Claude Desktop.

Select Chat (or Cowork) in the upper-left corner.
Install the npx command-line tool. This configuration requires npx.
- To install Node.js, download it from Node.js. Installing Node.js requires local admin permissions.
- Alternatively, if Homebrew is already installed, install Node.js (which includes npx) with Homebrew:
```
brew install node
```
- To verify the installation, run:
```
node --version
npm --version
```
This procedure works on macOS and should also work on Windows.
Open Claude Desktop, select Settings, select Developer, and then select Edit Config. The file explorer opens.
Choose claude_desktop_config.json and open it in your preferred editor.

Paste one of the following snippets into the file, and replace the placeholders with your real credentials.

Bitsight (SPM, CM, and/or VRM) only

{
    "mcpServers": {
        "bitsight-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@ownid/mcp-remote",
                "https://mcp.bitsighttech.com/mcp",
                "--header",
                "X-Bitsight-API-Token: <your-api-token-here>"
            ]
        }
    }
}

CTI only

{
    "mcpServers": {
        "bitsight-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@ownid/mcp-remote",
                "https://mcp.bitsighttech.com/mcp",
                "--header",
                "X-CTI-Client-ID: <your-cti-client-id>",
                "--header",
                "X-CTI-Client-Secret: <your-cti-client-secret>"
            ]
        }
    }
}

Combined (Bitsight SPM, CM, VRM, and CTI)

{
    "mcpServers": {
        "bitsight-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@ownid/mcp-remote",
                "https://mcp.bitsighttech.com/mcp",
                "--header",
                "X-Bitsight-API-Token: <your-api-token-here>",
                "--header",
                "X-CTI-Client-ID: <your-cti-client-id>",
                "--header",
                "X-CTI-Client-Secret: <your-cti-client-secret>"
            ]
        }
    }
}

Quit Claude Desktop fully and reopen it.
Start a new chat and click the tools icon. bitsight-mcp appears in the list.

Microsoft Windows (via mcp-proxy)

These instructions install mcp-proxy for Claude Desktop on Windows.

Install mcp-proxy (using uv and Git)

Install uv. Run the following command in a terminal, and then restart the terminal:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Install Git. Run the following command, and then restart the terminal:
```
winget install --id Git.Git -e --source winget
```

Install mcp-proxy. Run the following command:

uv tool install git+https://github.com/sparfenyuk/mcp-proxy

Find the mcp-proxy path. Run the following command to get the executable path:
```
where mcp-proxy
```
Copy this path into your configuration file in place of the <mcp-proxy-path> placeholder.

Important: In JSON configuration files, escape Windows backslashes by doubling them. For example, change C:\Users\user\.local\bin\mcp-proxy.exe to C:\\Users\\user\\.local\\bin\\mcp-proxy.exe.

Combined (Bitsight and CTI)

{
    "mcpServers": {
        "bitsight-mcp": {
            "command": "<mcp-proxy-path>",
            "args": [
                "--transport",
                "streamablehttp",
                "-H",
                "X-Bitsight-API-Token",
                "<your-api-token>",
                "-H",
                "X-CTI-Client-ID",
                "<your-cti-client-id>",
                "-H",
                "X-CTI-Client-Secret",
                "<your-cti-client-secret>",
                "https://mcp.bitsighttech.com/mcp"
            ]
        }
    }
}

Bitsight (SPM, CM, and/or VRM) only

{
    "mcpServers": {
        "bitsight-mcp": {
            "command": "<mcp-proxy-path>",
            "args": [
                "--transport",
                "streamablehttp",
                "-H",
                "X-Bitsight-API-Token",
                "<your-api-token-here>",
                "https://mcp.bitsighttech.com/mcp"
            ]
        }
    }
}

CTI only

{
    "mcpServers": {
        "bitsight-mcp": {
            "command": "<mcp-proxy-path>",
            "args": [
                "--transport",
                "streamablehttp",
                "-H",
                "X-CTI-Client-ID",
                "<your-cti-client-id>",
                "-H",
                "X-CTI-Client-Secret",
                "<your-cti-client-secret>",
                "https://mcp.bitsighttech.com/mcp"
            ]
        }
    }
}

ChatGPT

To set up an MCP server in ChatGPT, you need Developer mode and custom MCP apps enabled for your workspace. This feature is currently available for ChatGPT Business, Enterprise, and Edu workspaces, and admins or owners control availability. For details, see the OpenAI Help Center.

Click your account (bottom left), select Settings, select Apps, select Advanced Settings, and enable Developer mode.
Go back to Apps and click Create app next to Advanced Settings.
Enter a name (Bitsight MCP) and the server URL (https://mcp.bitsighttech.com/mcp). Then select either OAuth or Access token / API key.
If you selected Access token / API key, select Custom Header and enter X-Bitsight-API-Token.
Click Create. If you are using an API token, paste your API token on the next screen.
Confirm that the MCP is connected, and then close the settings dialog.

Publish Date or Recent Edits

October 26, 2026: Added instructions for how to add the Bitsight MCP connector from the Claude directory.
October 6, 2026: Published.

Connect to the Bitsight MCP server

Table of contents

Credentials

Authentication methods

OAuth

API credentials

Bitsight API token

CTI API client ID and secret

Configure your AI client

Quick start

CLI tools: simple mcp.json implementation

Generic Bitsight MCP

OAuth for Bitsight, CTI, or both

Get the Bitsight connector from the Claude directory

Claude Desktop (Code)

Claude Code (CLI)

VSCode, Cursor, Kiro (IDE)

Web and desktop tools

Claude Desktop (Chat and Cowork)

Claude Desktop (Chat and Cowork) without the custom connector option

Microsoft Windows (via mcp-proxy)

ChatGPT

Comments