@bbradar/mcp 0.1.12 → 0.1.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -0
- package/dist/server.js +855 -326
- package/dist/server.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -106,6 +106,12 @@ claude mcp add bbradar_io --scope user --env BBRADAR_API_KEY="your_pro_mcp_api_k
|
|
|
106
106
|
|
|
107
107
|
After adding the MCP config, restart your client and call `get_mcp_status`. A working setup returns server status, timing, and rate-limit metadata.
|
|
108
108
|
|
|
109
|
+
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.
|
|
110
|
+
|
|
111
|
+
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.
|
|
112
|
+
|
|
113
|
+
`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`.
|
|
114
|
+
|
|
109
115
|
## Tools
|
|
110
116
|
|
|
111
117
|
- `search_programs`
|
|
@@ -141,6 +147,7 @@ After adding the MCP config, restart your client and call `get_mcp_status`. A wo
|
|
|
141
147
|
- `find_recently_added_wildcards`
|
|
142
148
|
- `find_low_competition_high_reward`
|
|
143
149
|
- `get_program_delta`
|
|
150
|
+
- `get_bbradar_guide`
|
|
144
151
|
- `get_latest_added_targets`
|
|
145
152
|
- `get_program_scope_summary`
|
|
146
153
|
- `get_program_target_breakdown`
|