enrich_lead — B2B Lead Enrichment MCP Tool
enrich_lead
(enrich lead) is one of 1 tool on the
B2B Lead Enrichment
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call enrich_lead from your client
- Claude Code B2B Lead Enrichment enrich_lead run in your project directory
- Claude Desktop B2B Lead Enrichment enrich_lead ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor B2B Lead Enrichment enrich_lead ~/.cursor/mcp.json
- VS Code B2B Lead Enrichment enrich_lead .vscode/mcp.json
- Zed B2B Lead Enrichment enrich_lead ~/.config/zed/settings.json
- Windsurf B2B Lead Enrichment enrich_lead ~/.codeium/windsurf/mcp_config.json
- Cline B2B Lead Enrichment enrich_lead ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI B2B Lead Enrichment enrich_lead ~/.gemini/settings.json
- Grok B2B Lead Enrichment enrich_lead .mcp.json (in your project root)
- ChatGPT B2B Lead Enrichment enrich_lead Settings → Connectors → Advanced → Developer mode
- Claude.ai B2B Lead Enrichment enrich_lead Settings → Connectors → Add custom connector
- LangChain B2B Lead Enrichment enrich_lead pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lead-enrichment-mcp https://lead-enrichment-mcp.agent-infra.workers.dev/mcp
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.