# Connect bbradar to AI tools with MCP | bbradar.io
> Install the bbradar MCP server and use program opportunities, target intelligence, and Pro data in a compatible AI client.
Source: [https://bbradar.io/docs/mcp](https://bbradar.io/docs/mcp)
## [Prerequisites](https://bbradar.io/docs/mcp.md#prerequisites)
- Active bbradar Pro access
- A bbradar Pro API key
- Node.js 20 or newer
- An MCP client that supports local STDIO servers
The `@bbradar/mcp` package runs locally on your computer. It talks to the bbradar Pro API using your key and exposes structured tools to your MCP client.
These capabilities were checked against published version `0.2.3`. The installation commands select the current npm release; use `get_mcp_status` and `get_bbradar_guide` to check the version and tools installed in your client.
Check Node.js and run once
```
node --version
npx -y @bbradar/mcp
```
[Open @bbradar/mcp on npmReview the published package, current tools, and client examples.](https://www.npmjs.com/package/@bbradar/mcp)
## [Create an API key](https://bbradar.io/docs/mcp.md#create-key)
1. ### Open Account & Billing
Find the Pro API key card.
2. ### Create the key
Select **Create API key**. Each account has one active personal key.
3. ### Copy it immediately
The complete `bbr_live` secret is shown only once. Store it in your MCP client environment.
Sanitized product view
Your API key is ready
This secret is shown once.
bbr_live_demo_••••••••••••••••••••
Store it in your client environment, then close this dialog.
One-time API key dialog with the secret redacted. Example data and credentials are fictional or redacted; named product controls match the interface.
## [Install in your MCP client](https://bbradar.io/docs/mcp.md#install)
1. ### Choose the matching client section
Use the exact command or configuration shape for Codex, Claude Code, OpenCode, or your generic MCP client.
2. ### Insert your API key
Replace `YOUR_BBRADAR_API_KEY` locally. Do not paste the key into a prompt or share the finished configuration.
3. ### Add or save the server
Run the CLI command, or save the JSON in the configuration file used by your client.
4. ### Restart the client
Most clients load local STDIO server configuration only during startup.
### Codex CLI
Terminal
```
codex mcp add bbradar_io --env BBRADAR_API_KEY="YOUR_BBRADAR_API_KEY" -- npx -y @bbradar/mcp
```
### Claude Code
Terminal
```
claude mcp add bbradar_io --scope user --env BBRADAR_API_KEY="YOUR_BBRADAR_API_KEY" -- npx -y @bbradar/mcp
```
### OpenCode
Add the local server to your OpenCode configuration:
opencode.json
```
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bbradar.io": {
"type": "local",
"command": ["npx", "-y", "@bbradar/mcp"],
"enabled": true,
"timeout": 30000,
"environment": {
"BBRADAR_API_KEY": "YOUR_BBRADAR_API_KEY"
}
}
}
}
```
### Generic JSON configuration
MCP client configuration
```
{
"mcpServers": {
"bbradar.io": {
"command": "npx",
"args": ["-y", "@bbradar/mcp"],
"env": {
"BBRADAR_API_KEY": "YOUR_BBRADAR_API_KEY"
}
}
}
}
```
Windows clients
If a native Windows client cannot launch `npx` directly, set the command to `cmd` and begin the arguments with `/c`, `npx`. For Claude Code, place `cmd /c` immediately before `npx` in the command above.
## [Verify the connection](https://bbradar.io/docs/mcp.md#verify-mcp)
1. ### Restart or reload your MCP client
Clients normally read local server configuration at startup.
2. ### Run get_mcp_status
Confirm the server is connected, authentication is valid, and Pro access is active.
3. ### Run get_bbradar_guide
Use the built-in guide to discover the available bbradar tools and their parameters.
4. ### Try a narrow query
Ask for a small program or opportunity result before requesting large target or change feeds.
Sanitized product view
MCP client
$ get_mcp_status
server bbradar_io
status connected
access pro
tools programs, opportunities, targets, target_changes, repository_changes
Authentication verified
MCP server status after a successful bbradar connection. Example data and credentials are fictional or redacted; named product controls match the interface.
## [Available data and limitations](https://bbradar.io/docs/mcp.md#mcp-capabilities)
| Data | Available through MCP | Notes |
| --- | --- | --- |
| Programs | Yes | Paginated platform and Self-Hosted program data with server-side name, handle, platform, policy-host, and target search. |
| Self-Hosted program profiles | Yes | Exact program lookup, rewards, policy and reporting routes, structured scope, and capability markers. |
| Opportunity tiers | Yes | Elite, Hot, Strong, and Potential programs with the score factors and reason returned by the API. |
| Program targets | Yes | Active target identities for platform and Self-Hosted programs. Target scoring and dupe-risk fields appear only when their source signals exist. |
| Target changes | Yes | Page browsing plus bounded incremental cursor polling with the same target-intelligence fields. |
| Repository changes | Yes (MCP 0.2.3) | get_repository_changes provides a bounded platform feed, compact program summaries, and incremental cursors. Repository quality fields are not all projected by this package version. |
| Program History | No | The per-program History timeline currently requires a signed-in Pro browser session. It is not an API key endpoint or MCP tool. |
Run `get_bbradar_guide` in your client for the installed package’s current tool parameters. MCP uses the Pro API and preserves `data_capabilities`, so clients can distinguish an unsupported signal from a real zero or empty result.
API and MCP versions differ
MCP 0.2.3 supports repository feeds, but does not expose the API’s snapshot parameter or every newer scoring, fee-range, and repository-quality field in compact responses. Use the [HTTP API reference](https://bbradar.io/docs/api.md) when your workflow needs those fields or stable snapshot pages.
## [Keep your key safe](https://bbradar.io/docs/mcp.md#key-safety)
- Put the key in the MCP client environment, not prompts
- Do not commit client configuration containing the secret
- Do not paste the key into chat or support messages
- Regenerate immediately if the secret may have leaked
Security
Selecting **Regenerate** invalidates the previous secret immediately. Update every API script and MCP client that used it. Selecting **Delete** stops all API and MCP access until you create another key.