Connect Bitsight MCP to Microsoft 365 Copilot through Copilot Studio

Microsoft 365 Copilot connects to the Bitsight MCP (Model Context Protocol) through an agent built in Microsoft Copilot Studio. A maker creates the agent once, adds the Bitsight MCP as a tool, and publishes the agent to Microsoft 365 Copilot and Teams. Each user then connects the agent with their own Bitsight credentials.

This article explains how to build, publish, and connect the agent.

Applies to: Makers who build and publish Copilot Studio agents and end users who use the agent in Microsoft 365 Copilot

Before you begin

Makers (person building the agent) need:

  • Access to Microsoft Copilot Studio with permission to create and publish agents
  • Bitsight credentials for the products you'll use (see Credentials above)
  • Confirmation from your Power Platform admin that your environment's data policies allow Model Context Protocol tools

End users need:

  • A Microsoft 365 Copilot license
  • Membership in the users or groups the agent is shared with
  • Their own Bitsight credentials

Choose your authentication method

You need access to Use
Bitsight (SPM, CM, VRM), Bitsight CTI, or both OAuth (recommended for Copilot)
Bitsight (SPM, CM, VRM) only, and you prefer an API token API key (header X-Bitsight-API-Token)
Bitsight CTI only, and you prefer API credentials API key (header X-CTI-Client-Key)

Copilot Studio sends only one authentication header per MCP connection. That works for Bitsight alone (API token) and for Bitsight CTI alone (a single X-CTI-Client-Key header that combines your CTI client ID and client secret). It does not work for a single connection that combines Bitsight and Bitsight CTI, because that requires multiple headers.

To use Bitsight and Bitsight CTI together, use OAuth. OAuth works for every combination. If you prefer API credentials, you can instead add the Bitsight MCP to your agent twice, once with the Bitsight API token and once with the CTI key.

Instructions

Step 1: Create the agent

  1. Sign in to Microsoft Copilot Studio.
  2. In the left navigation pane, select Create, and then select New agent.
  3. Enter a name and description users will recognize, for example:
    1. Name: Bitsight
    2. Description: Ask questions about your Bitsight ratings, portfolio, findings, vendors, and threat intelligence.
  4. (Optional) Add instructions, for example: "Use the Bitsight MCP tool to answer questions about Bitsight ratings, companies, portfolios, findings, alerts, and threat intelligence. Tell the user which tools you used."
  5. Select Create.

Step 2: Add the Bitsight MCP tool

  1. In the agent configuration, select Tools, and then select Add a tool.
  2. Select New tool, and then select Model Context Protocol.
  3. Enter the server details:
    • Server name: Bitsight MCP
    • Server description: Bitsight security ratings, portfolio, findings, vendor risk, and threat intelligence data. The agent uses this description to decide when to call the server, so keep it specific.
    • Server URL: https://mcp.bitsighttech.com/mcp

Read-only access: To limit the agent to reading data, use this server URL instead: https://mcp.bitsighttech.com/mcp?readonly=true. The server then hides all write actions, so the agent never sees them and doesn't offer to perform them.

4. Configure authentication using one of the options below.

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

  • Authentication: OAuth 2.0
  • Type: Dynamic discovery

Select Create. Copilot Studio registers itself with the Bitsight MCP automatically, so you don't need a client ID or secret.

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

  • Authentication: API key
  • Type: Header
  • Header name: X-Bitsight-API-Token

Select Create.

Option C: API key (Bitsight CTI only)

  • Authentication: API key
  • Type: Header
  • Header name: X-CTI-Client-Key

Select Create.

Step 3: Create your connection

  1. On the Add tool screen, open the Connection dropdown and select Create new connection, and then select Create.
  2. Complete sign-in for the option you chose:
    1. 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.
    2. API key (Bitsight): Paste your Bitsight API token. Paste the token only, without a "Bearer" prefix.
    3. API key (CTI): Enter your CTI API client ID and API client secret in the format <client_id>:<client_secret>, with a colon between them and no spaces.
  3. Select Add and configure.

Step 4: Review the tool settings

  1. In the Tools section, select Bitsight MCP to view the list of tools the server exposes.
  2. Read-only access: If you used the read-only server URL in Step 2, confirm that invoke_mutate_api does not appear in the list.
  3. Credentials: Confirm the tool uses end-user credentials, so each person connects with their own Bitsight account and sees only the data that account can access. Avoid sharing the maker's connection with all users.

Step 5: Publish and share the agent

  1. On the agent configuration screen, select Publish.
  2. Select the menu button (three dots) at the top right of the page, and then select Share.
  3. Add the users or groups who should have access, assign the Viewer role, and then select Update.
  4. Select Channels, select Teams and Microsoft 365 Copilot, and then select Add channel.
  5. Copy the links Copilot Studio displays and share them with your users.

Depending on your organization's settings, a Microsoft 365 admin may need to approve the agent before it appears for users.

Step 6: Connect as an end user

  1. Sign in to Microsoft 365 Copilot and add the Bitsight agent from the left pane, or open the link your admin shared.
  2. Ask a test question, for example: "Using the Bitsight MCP, what is my user info at Bitsight?"
  3. The first time you use the agent, Copilot prompts you to connect:
    1. Select Open Connection Manager, and then select Connect.
    2. Select the menu button (three dots), and then select Add new connection.
    3. OAuth: Select Bitsight, CTI, or Bitsight+CTI, and then sign in. API key: Paste your Bitsight API token, or for CTI, your <client_id>:<client_secret> value.
    4. Select Submit, return to the chat, and select Retry.
  4. The agent returns your Bitsight user information.

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.

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

Your token or session may have expired.

  • For API key connections, generate a new token in Bitsight (Account Settings > User API Token) or a new CTI secret, and update your connection in Connection Manager.
  • For OAuth connections, remove and re-add the connection to 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.
  • If you used OAuth, confirm you selected CTI or Bitsight+CTI during sign-in. If you selected Bitsight+CTI and your organization has no CTI API package, the sign-in quietly falls back to Bitsight only. Contact your Bitsight account team to confirm your CTI API access.
  • If you used an API key connection, confirm the header is X-CTI-Client-Key and the value is <client_id>:<client_secret>. A connection that uses X-Bitsight-API-Token returns Bitsight (SPM, CM, VRM) data only.
The agent answers without using Bitsight data.

Start your question with "Using the Bitsight MCP," or ask the agent to list the tools and APIs it used. A specific server description (Step 2) also helps.

The Model Context Protocol tool cannot be added.

Your Power Platform data policies may block it. Contact your Power Platform administrator.

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.