This page explains how to connect the BriteCore Connector to Anthropic, OpenAI, and Cursor clients. Each client uses the same BriteCore tenant URL and browser-based BriteCore sign-in. You do not need to copy or store an access token.
Once connected, your AI assistant can work with policies, claims, quotes, underwriting rules, reports, and forms. Available actions depend on your BriteCore role. Your client may ask for confirmation before changing data.
What you need first
Before connecting, gather the following:
- **A BriteCore tenant URL.** For production deployments your URL is `https://<your-tenant>.britecorepro.com/mcp`. See [Tenants and URLs](./tenants-and-urls.md).
- **An active BriteCore account.** The client opens the BriteCore sign-in when it first connects. Your connection applies only to your BriteCore tenant. See [Authentication](./authentication.md) for sign-in and role selection.
Anthropic
Choose the Marketplace Connector after BriteCore appears in Anthropic's Connectors Directory. Use the Custom Connector when a BriteCore administrator gives you a tenant URL directly.
Marketplace connector
- Open Claude or Claude Desktop.
- Open **Customize > Connectors**, then select the **+** button.
- Browse the Connectors Directory and select **BriteCore Connector**.
- Review the listed capabilities and read/write permissions.
- Select **Connect** or **Install**, then finish the BriteCore sign-in.
- In a conversation, open the **+** menu, select **Connectors**, and enable BriteCore for that conversation.
Team and Enterprise Owners may need to add BriteCore to the organization before members can connect their accounts. See [Anthropic's directory instructions](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities) for organization and tool-permission controls.
Custom connector
Use this route when BriteCore provides an exact tenant URL and your organization allows custom remote MCP connectors.
Claude on the web and Claude Desktop
Claude and Claude Desktop share connector settings. Team and Enterprise organizations may require an Owner to add the connector before members can use it.
- Open **Customize > Connectors**.
- Select the **+** button, then **Add custom connector**.
- Enter `BriteCore Connector` as the name and your tenant URL as the remote MCP URL.
- Leave the optional OAuth Client ID and Client Secret empty.
- Select **Add**, then **Connect**, and finish the BriteCore sign-in.
- In a conversation, open the **+** menu, select **Connectors**, and enable BriteCore for that conversation.
See [Anthropic's custom connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for plan and organization controls.
Claude Code
Add BriteCore from a terminal:
```bash
claude mcp add --transport http britecore https://<tenant>.britecorepro.com/mcp
```
Start Claude Code and enter `/mcp`. Select `britecore`, authenticate, and finish the browser sign-in. Use `claude mcp list` to check the connection. See the [Claude Code MCP guide](https://code.claude.com/docs/en/mcp) for configuration scopes and authentication management.
OpenAI
ChatGPT desktop app
- Open **Settings > MCP servers**.
- Select **Add server**.
- Enter `BriteCore` as the name, choose **Streamable HTTP**, and enter your tenant URL.
- Save the server and restart the app.
- Return to **MCP servers** and select **Authenticate** for BriteCore.
- Finish the browser sign-in. Enter `/mcp` in the composer to check the connection.
ChatGPT on the web
ChatGPT web uses BriteCore through an installed plugin. Once the BriteCore plugin is available to your workspace, install it from the **Plugins** tab, connect your BriteCore account, and enable its tools in the conversation.
Codex CLI and IDE extension
Add BriteCore and sign in from a terminal:
```bash
codex mcp add britecore --url https://<tenant>.britecorepro.com/mcp
codex mcp login britecore
codex mcp list
```
The ChatGPT desktop app, Codex CLI, and Codex IDE extension share MCP settings on the same computer. In the IDE extension, open the gear menu and select **MCP servers** to inspect or authenticate the connection. See the [official OpenAI MCP documentation](https://learn.chatgpt.com/docs/extend/mcp)
for configuration and approval options.
Cursor
Add BriteCore to `~/.cursor/mcp.json` for all projects, or to `.cursor/mcp.json` for one project:
```json
{
"mcpServers": {
"britecore": {
"url": "https://<tenant>.britecorepro.com/mcp"
}
}
}
```
Save the file and restart Cursor. Open **Customize > MCP**, find `britecore`, and finish the BriteCore sign-in. Cursor Agent CLI users can authenticate and check the available tools with:
```bash
cursor-agent mcp login britecore
cursor-agent mcp list-tools britecore
```
Do not add OAuth credentials or authorization headers. The browser sign-in handles authentication. See the
[Cursor MCP documentation](https://cursor.com/docs/mcp) for configuration locations and team controls.
Verify the connection
Ask the client to list the perils available for a claim. This calls `get_all_perils` with no arguments. Expect your carrier's peril list. If you receive a `FORBIDDEN` response, ask your BriteCore administrator to check your role's permissions.
If BriteCore offers more than one role, use `list_my_roles`, then `select_my_role`, before using business tools. See [Authentication](./authentication.md) for role-selection instructions.
What's next
- [User guide](./user-guide.md) provides example prompts for each business
area. - [Capabilities](./capabilities.md) describes the available business tools.
- [Authentication](./authentication.md) covers sign-in, role selection, and reconnection.
- [Tenants and URLs](./tenants-and-urls.md) explains the per-tenant URL pattern.
- [Support](./support.md) lists troubleshooting steps and contact details.
