@bbradar/mcp

Local STDIO MCP server for bbradar.io Pro subscribers. It lets MCP clients query bbradar.io Pro program, target, opportunity, and recent-change data through a local npm package.

Requirements

• Node.js 20 or newer.
• A bbradar.io Pro API key.
• An MCP client that supports local STDIO servers.

Install

Most MCP clients can run the package directly with npx:

npx -y @bbradar/mcp

For a global install:

npm install -g @bbradar/mcp
bbradar-mcp

For a project-local install:

npm install @bbradar/mcp
npx bbradar-mcp

The server needs your bbradar.io Pro key. In the MCP client config, add it as BBRADAR_API_KEY.

Client Configuration

OpenCode

{
  "$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_pro_mcp_api_key"
      }
    }
  }
}

Codex

Add with the Codex CLI:

codex mcp add bbradar_io --env BBRADAR_API_KEY="your_pro_mcp_api_key" -- npx -y @bbradar/mcp

Or add it to ~/.codex/config.toml:

[mcp_servers.bbradar_io]
command = "npx"
args = ["-y", "@bbradar/mcp"]

[mcp_servers.bbradar_io.env]
BBRADAR_API_KEY = "your_pro_mcp_api_key"

Claude Code

Add a private user-level server:

claude mcp add bbradar_io --scope user --env BBRADAR_API_KEY="your_pro_mcp_api_key" -- npx -y @bbradar/mcp

On native Windows, wrap npx with cmd /c:

claude mcp add bbradar_io --scope user --env BBRADAR_API_KEY="your_pro_mcp_api_key" -- cmd /c npx -y @bbradar/mcp

Generic MCP JSON

{
  "mcpServers": {
    "bbradar.io": {
      "command": "npx",
      "args": ["-y", "@bbradar/mcp"],
      "env": {
        "BBRADAR_API_KEY": "your_pro_mcp_api_key"
      }
    }
  }
}

Verify

After adding the MCP config, restart your client and call get_mcp_status. A working setup returns server status, timing, and rate-limit metadata.

For simple tool selection, call get_bbradar_guide. It returns the recommended entry points, common filter meanings, and example calls without contacting the BBRadar API.

Most tools that accept program_id also accept a human program name or handle. The server resolves names automatically when there is one clear match; for ambiguous names, call resolve_program first and retry with the returned platform:handle id.

find_programs_by_target defaults to flexible target matching. It accepts bare domains, full URLs, wildcard scopes, target names, package/repo-style identifiers, or short phrases like known api target.

Tools

• search_programs
• get_program
• resolve_program
• run_program_name_action
• get_program_targets
• get_recent_changes
• get_opportunities
• find_programs
• find_wildcard_programs
• find_web3_programs
• find_reward_programs
• find_web3_contests
• find_language_programs
• find_target_type_programs
• find_vdp_programs
• find_paid_programs
• find_stack_matches
• find_low_noise_programs
• find_recent_by_type
• find_recently_updated_programs
• find_programs_by_target
• find_program_candidates
• find_hunt_candidates
• find_fresh_hunt_candidates
• list_filters
• get_mcp_status
• compare_programs
• compare_programs_compact
• summarize_program_activity
• get_program_brief
• find_recently_added_wildcards
• find_low_competition_high_reward
• get_program_delta
• get_bbradar_guide
• get_latest_added_targets
• get_program_scope_summary
• get_program_target_breakdown
• get_program_scope_delta
• get_recent_target_activity
• check_program_new_targets
• check_watchlist_new_targets
• export_targets

Prompts

• find_best_programs_to_hunt
• summarize_program_scope
• prepare_recon_plan