This article is for organisation administrators setting up the Brightflag MCP connector in Claude for the first time. Complete the steps below before standard users attempt to connect.
Note. The Brightflag connector is currently in beta. Functionality and screens may change.
Before you start
You will need the MCP URL provided to you by your Brightflag account team. If you do not have it, contact your Brightflag account team before proceeding.
Step 1: Choose a connection method
Brightflag supports two ways to register the connector with Claude. Choose whichever fits your organisation's security requirements. Both use the same MCP URL and lead to the same experience for end users.
Dynamic registration. Most organisations can use this option. When you add the Brightflag connector, Claude and Brightflag exchange registration details automatically (using a Client ID Metadata Document, or CIMD), so no clientId is needed. This is the fastest path and needs nothing from your Brightflag account team beyond the MCP URL.
Pre-registered client. If your organisation's security policy requires every OAuth client to be explicitly pre-approved, contact your Brightflag account team for a dedicated clientId and secret. You will enter these in Advanced Settings in Step 2.
Step 2: Create a custom connector for your organisation
This step registers Brightflag as a connector inside your organisation's Claude settings, making it available to be enabled for users.
Go to organisation settings.
Go to Connectors.
Select Add, then Custom, then Web.
The Connectors page in organisation settings, with Add > Custom > Web selected.
Complete the Add Custom Connector form:
Name it Brightflag.
Use the MCP URL provided to you by Brightflag.
If you are using a pre-registered client (see Step 1), open Advanced Settings and add the clientId and secret provided to you by Brightflag. Otherwise, leave this blank.
Select Add.
The Add custom connector form, with the Brightflag MCP URL entered. The clientId and secret are added under Advanced settings only if using a pre-registered client.
Done. Brightflag now appears as a connector option in your organisation's settings. Continue to Step 3 if your organisation uses custom roles, or skip it if it does not.
Step 3: Enable the connector for users (custom roles only)
If your organisation uses custom roles to manage feature access, you will need to explicitly allow the Brightflag connector on the relevant roles before users can connect to it. If your organisation does not use custom roles, you can skip this step.
Edit an existing custom role, or create a new one.
Go to the Connectors tab in the edit or create role modal.
Find the Brightflag connector and set it to Always allow.
The Connectors tab of the Edit role modal, with the Brightflag connector set to Always allow.
Repeat this for every role that should have access to Brightflag. Once complete, users assigned to those roles will be able to connect to Brightflag from their own account.
What happens next
Let your users know they can now connect their own accounts. Point them to Connecting to Brightflag in Claude for the steps.
s. Continue to Step 2 if your organisation uses custom roles, or skip it if it does not. |
Step 2: Enable the connector for users (custom roles only)
If your organisation uses custom roles to manage feature access, you will need to explicitly allow the Brightflag connector on the relevant roles before users can connect to it. If your organisation does not use custom roles, you can skip this step.
Edit an existing custom role, or create a new one.
Go to the Connectors tab in the edit or create role modal.
Find the Brightflag connector and set it to Always allow.
The Connectors tab of the Edit role modal, with the Brightflag connector set to Always allow.
Repeat this for every role that should have access to Brightflag. Once complete, users assigned to those roles will be able to connect to Brightflag from their own account.
What happens next
Let your users know they can now connect their own accounts. Point them to Connecting to Brightflag in Claude for the steps.