analyze_buyer_intelligence — buyer intelligence MCP Tool
analyze_buyer_intelligence
(analyze buyer intelligence) is one of 13 tools on the
buyer intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_buyer_intelligence from your client
- Claude Code buyer intelligence analyze_buyer_intelligence run in your project directory
- Claude Desktop buyer intelligence analyze_buyer_intelligence ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor buyer intelligence analyze_buyer_intelligence ~/.cursor/mcp.json
- VS Code buyer intelligence analyze_buyer_intelligence .vscode/mcp.json
- Zed buyer intelligence analyze_buyer_intelligence ~/.config/zed/settings.json
- Windsurf buyer intelligence analyze_buyer_intelligence ~/.codeium/windsurf/mcp_config.json
- Cline buyer intelligence analyze_buyer_intelligence ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI buyer intelligence analyze_buyer_intelligence ~/.gemini/settings.json
- Grok buyer intelligence analyze_buyer_intelligence .mcp.json (in your project root)
- ChatGPT buyer intelligence analyze_buyer_intelligence Settings → Connectors → Advanced → Developer mode
- Claude.ai buyer intelligence analyze_buyer_intelligence Settings → Connectors → Add custom connector
- LangChain buyer intelligence analyze_buyer_intelligence pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http buyer-intelligence https://www.procureradar.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.