bbradar.io
Browse documentation
bbradar Pro guide

Connect bbradar to AI tools with MCP

Install the bbradar MCP server and use program opportunities, target intelligence, and Pro data in a compatible AI client.

10 min readReviewed Read as Markdown
On this page

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.

Create an API 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
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

  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"
      }
    }
  }
}

Verify the connection

  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 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

Data
Programs
Available through MCP
Yes
Notes
Paginated platform and Self-Hosted program data with server-side name, handle, platform, policy-host, and target search.
Data
Self-Hosted program profiles
Available through MCP
Yes
Notes
Exact program lookup, rewards, policy and reporting routes, structured scope, and capability markers.
Data
Opportunity tiers
Available through MCP
Yes
Notes
Elite, Hot, Strong, and Potential programs with the score factors and reason returned by the API.
Data
Program targets
Available through MCP
Yes
Notes
Active target identities for platform and Self-Hosted programs. Target scoring and dupe-risk fields appear only when their source signals exist.
Data
Target changes
Available through MCP
Yes
Notes
Page browsing plus bounded incremental cursor polling with the same target-intelligence fields.
Data
Repository changes
Available through MCP
Yes (MCP 0.2.3)
Notes
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.

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.

Keep your key safe

  • 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