enrich_buyer_contact — buyer intelligence MCP Tool
enrich_buyer_contact
(enrich buyer contact) 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 enrich_buyer_contact from your client
- Claude Code buyer intelligence enrich_buyer_contact run in your project directory
- Claude Desktop buyer intelligence enrich_buyer_contact ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor buyer intelligence enrich_buyer_contact ~/.cursor/mcp.json
- VS Code buyer intelligence enrich_buyer_contact .vscode/mcp.json
- Zed buyer intelligence enrich_buyer_contact ~/.config/zed/settings.json
- Windsurf buyer intelligence enrich_buyer_contact ~/.codeium/windsurf/mcp_config.json
- Cline buyer intelligence enrich_buyer_contact ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI buyer intelligence enrich_buyer_contact ~/.gemini/settings.json
- Grok buyer intelligence enrich_buyer_contact .mcp.json (in your project root)
- ChatGPT buyer intelligence enrich_buyer_contact Settings → Connectors → Advanced → Developer mode
- Claude.ai buyer intelligence enrich_buyer_contact Settings → Connectors → Add custom connector
- LangChain buyer intelligence enrich_buyer_contact 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.