Step-by-step guide to configuring the Bitsight MCP server in Claude, ChatGPT, and Cursor so your AI assistant can monitor vendor risk in plain language.
Third-party risk, governance, risk and compliance (GRC), and security operations teams increasingly want their AI assistant to pull live vendor cyber risk data on demand, instead of toggling between dashboards and spreadsheets. The Model Context Protocol (MCP) is the open standard that makes that possible. Our hosted MCP server at https://mcp.bitsighttech.com/mcp connects Claude, ChatGPT, Cursor, VS Code, Kiro, and Microsoft Copilot to seven core MCP tools and more than 1,000 Bitsight API operations covering ratings, findings, alerts, vendor portfolios and threat intelligence. This guide walks through what MCP is, why it matters in 2026, step-by-step setup for each client, continuous vendor monitoring workflows, permissions and data handling, and answers to the questions we hear most often.
What is an MCP server for vendor risk monitoring?
The Model Context Protocol (MCP) is an open standard developed by Anthropic and introduced on November 25, 2024, that gives AI assistants a consistent way to reach outside tools and data. The protocol separates three roles: the MCP host (the application the user interacts with, such as Claude Desktop or Cursor), the MCP client (the connector inside that host), and the MCP server (the external system that exposes data and actions).
An MCP server for vendor risk monitoring exposes vendor ratings, findings, risk vectors, vendor intelligence, and threat intelligence to an AI assistant so a third-party risk or GRC analyst can ask questions in plain language instead of writing API calls. The Bitsight MCP is our own server and a leading option in this category: it gives an MCP-compatible assistant, such as Claude, ChatGPT, or Microsoft Copilot, direct access to your Bitsight data and the full Bitsight API. It exposes seven core tools, covering API discovery, schema inspection, Knowledge Base search, and read and write operations, backed by more than 1,000 Bitsight API operations across ratings, findings, risk vectors, vendor intelligence, vulnerability context, and threat intelligence.
Why MCP servers for vendor risk monitoring matter in 2026
Vendor alert volumes keep climbing, and risk and security teams cannot keep pace through manual triage alone. Our MCP server and agentic capabilities close that gap by letting AI agents pull Bitsight ratings, findings and alerts at machine speed from a single intelligence platform, bridging the long-standing divide between risk and security work. An MCP-enabled environment now resembles a dynamic supply chain: you trust the model, the host application, every MCP server it reaches, the tools those servers expose and the credentials behind them. That is why an authenticated, vendor-backed MCP matters.
Common challenges in vendor risk monitoring and how an MCP server solves them
Third-party risk and GRC teams tell us the same story across onboarding, continuous monitoring, and offboarding: portfolios keep growing, alerts keep multiplying, and analyst headcount does not. Our Vendor Risk Management product exists to take the complexity out of managing that lifecycle, and Continuous Monitoring layers on objective data with a proven correlation to security incidents. The Bitsight MCP server extends both into the AI tools analysts already use, so a question like "which vendors declined this week?" returns an answer in seconds instead of a CSV export and a spreadsheet.
Key Problems Encountered
- Fragmented alerts across a growing vendor portfolio. As the number of monitored vendors climbs, teams lose the ability to see which alerts actually matter across onboarding, ongoing oversight, and offboarding stages.
- Manual API and CSV exports slow triage. Pulling ratings, findings, and alerts by hand through API scripts or portal exports adds hours between a risk signal and a decision.
- Analyst capacity does not scale with alert volume. Alert surges from new vendors, emerging CVEs, and underground activity outpace the number of reviewers available to read them.
- Inconsistent human-in-the-loop handoffs for vendor outreach. Without a shared workflow, escalations to vendor owners and procurement vary by analyst and get lost between tools.
The Bitsight MCP server addresses each of these directly. Vendor Risk Management handles portfolio-wide lifecycle complexity, Continuous Monitoring supplies the underlying signal, and the MCP lets AI agents and agentic GRC workflows consume that intelligence at machine speed without human-in-the-loop data retrieval. Because third-party risk management, exposure management, continuous monitoring and cyber threat intelligence sit on one Bitsight platform, analysts can triage, prioritize, and route vendor issues from a single conversation with their assistant and keep the final outreach decision with a human.
What to look for in an MCP server for vendor risk monitoring
Before you wire an AI assistant into your third-party risk program, evaluate any Model Context Protocol (MCP) server against a short list of operational, security and coverage criteria. The right server should be reachable from the assistants your team already uses, respect the permissions you have already set in your cyber risk platform, cover the data your analysts actually ask about (ratings, findings, risk vectors, vendor intelligence and threat intelligence), encrypt traffic end to end, keep your prompts out of model training, and let you move from read-only questions to controlled write actions when you are ready.
Must-have features
- Hosted remote MCP endpoint with OAuth sign-in so analysts can connect from Claude, Cursor, VS Code or ChatGPT without running their own server.
- Role-respecting identity model that inherits each user's existing permissions, access groups and product subscriptions rather than granting a shared service account.
- Broad data coverage across security ratings, findings, risk vectors, vendor portfolios, vulnerability context and threat intelligence, exposed through the vendor's full API surface.
- Encrypted traffic and a secure proxy design between the assistant, the MCP server and the underlying platform.
- A written commitment that API calls, prompts and responses are not used to train AI or machine learning models.
- Support for both read and write operations with explicit, auditable controls over which actions the agent can take.
Bitsight's MCP server meets each of these criteria out of the box. It is hosted at https://mcp.bitsighttech.com/mcp, supports OAuth through the assistant's connector settings, and is listed in the Claude Connector Directory so Claude users can add it in a few clicks. It uses your own Bitsight identity and honors your access controls, access groups and product subscriptions, so it never grants broader access than you already have. The seven core tools let the assistant discover and call any of Bitsight's 1,000+ API operations covering ratings, findings, risk vectors, vendor intelligence, vulnerability context and threat intelligence. It runs as a secure proxy with encrypted traffic, we do not use MCP traffic to train AI or machine learning models, and it supports both read and write operations so you can scale from Q&A to agentic workflows on your own terms.
How to set up the Bitsight MCP server in Claude, ChatGPT, and Cursor
Before you connect anything, confirm two prerequisites. First, you need an active Bitsight subscription to at least one product the MCP can surface data from: Security Posture Management (SPM), Continuous Monitoring (CM), Vendor Risk Management (VRM), or Bitsight Cyber Threat Intelligence (CTI). The MCP uses your own Bitsight identity and respects your existing role-based access controls, access groups, and product subscriptions, so it will not grant anything you do not already have. Second, you need an MCP-compatible assistant: Claude, ChatGPT, or an IDE such as Cursor, VS Code, or Kiro. In every client below, the server URL is the same: https://mcp.bitsighttech.com/mcp.
Setting up Bitsight MCP in Claude (directory and Claude Code)
- Open the Claude Connector Directory at claude.ai/directory/bitsight.
- Click Connect (or Add) and review the permissions Claude will request.
- Approve the connector, then sign in to Bitsight when the OAuth window opens. Claude never sees your Bitsight password.
- Return to Claude, open Customize > Connectors, and confirm that bitsight-mcp is listed and enabled.
- For Claude Code, create a project-scoped .mcp.json file in your project folder, or run: claude mcp add --scope project bitsight-mcp --transport http https://mcp.bitsighttech.com/mcp --header "X-Bitsight-API-Token: <api-token>". Use --scope user to make it available across all projects.
The directory listing is the fastest path for most analysts because it handles the OAuth sign-in for you, and you choose whether to connect Bitsight, CTI, or both. Claude Code is the better option for engineers who want the connection scoped to a specific repository and checked into version control with teammates. If you are on a free Claude account you can only add one custom connector, and enterprise IT may disable custom connectors entirely, so coordinate with your admin before you start.
Setting up Bitsight MCP in Cursor, VS Code, and Kiro
- Open the MCP configuration file for your IDE: ~/.cursor/mcp.json for Cursor, ~/.vscode/mcp.json for VS Code, or ~/.kiro/settings/mcp.json for Kiro.
- Add an entry named bitsight-mcp with the transport set to http and the URL https://mcp.bitsighttech.com/mcp.
- Save the file. Without any headers, the IDE will open a browser window for OAuth sign-in the first time a tool is called.
- Sign in to Bitsight and, when prompted, choose Bitsight, CTI, or both.
- Reopen the MCP panel in the IDE and confirm that bitsight-mcp shows a green connected state with its tools enabled.
OAuth is the simplest path in an IDE because the browser handles the sign-in and token refresh for you. If your workflow needs headless access, for example to run the MCP inside a long-running coding agent, the same config file accepts an X-Bitsight-API-Token header for SPM, CM, and VRM, plus X-CTI-Client-ID and X-CTI-Client-Secret for CTI. We recommend header-based credentials in any environment where the IDE cannot open a browser window reliably.
Setting up Bitsight MCP in ChatGPT Developer mode
- Confirm you are on a ChatGPT Business, Enterprise, or Edu workspace. Developer mode and custom MCP apps are not available on Free, Plus, or Pro plans, and your workspace admin controls whether they are enabled.
- Open Settings > Apps > Advanced Settings and turn on Developer mode.
- Choose Create app, name it Bitsight MCP, and enter https://mcp.bitsighttech.com/mcp as the server URL.
- Select an authentication method: OAuth, or Access token / API key using the custom header X-Bitsight-API-Token.
- Click Create (paste your API token on the next screen if you chose a token), then confirm the MCP shows as connected.
OAuth is the easiest option for individual analysts and keeps the connection tied to each user's Bitsight identity. If you use the access-token option, keep tokens one-to-one with named users so audit logs stay meaningful.
Verify the connection. In any client, open a fresh chat and ask the assistant to list the Bitsight tools it can call. You should see the seven core MCP tools, covering API discovery and schemas, Knowledge Base search, and read and write operations against more than 1,000 Bitsight API endpoints. Follow up with a low-risk read query such as "Show me my portfolio's current ratings" to confirm the OAuth session is active and traffic is flowing through the encrypted proxy to Bitsight.