Apollo Salesforce Mapper
Map Apollo prospect exports into Salesforce Lead fields with deterministic validation before your CRM sync jobs run.
Overview
dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper is a MCP server for the Grow phase that maps Apollo leads into Salesforce with strict required-field checks and PASS/REPAIR/FAIL verdicts.
What is this MCP server?
- Apollo-to-Salesforce Lead field mapping without an LLM in the loop
- Strict-fail on missing required fields so incomplete rows never slip through
- PASS, REPAIR, and FAIL verdicts for batch review and agent-driven fixes
- Remote streamable-http MCP at cf-worker.selbyventurecap.workers.dev
- Server version 2.0.0 aligned to the MCP server schema
- No LLM in the mapping pipeline
- Three verdict states: PASS, REPAIR, FAIL
What problem does it solve?
Apollo exports and Salesforce Lead schemas disagree on required fields, so automated syncs quietly create incomplete CRM records.
Who is it for?
Solo founders or tiny sales ops teams piping Apollo into Salesforce via an MCP-aware agent who want rule-based mapping, not LLM guesswork.
Skip if: Builders who need bi-directional Salesforce sync, custom object mapping beyond Leads, or AI-generated enrichment narratives.
What do I get? / Deliverables
After you register the server, your agent can validate and classify each mapped lead before import so only PASS rows sync and REPAIR/FAIL rows get explicit follow-up.
- Mapped Lead field payloads aligned to your Salesforce schema
- Per-record PASS, REPAIR, or FAIL verdicts for import decisions
- Actionable lists of missing required fields on strict-fail rows
Recommended MCP Servers
Journey fit
Lead ingestion and CRM hygiene sit in the grow phase where outbound and pipeline tooling must stay accurate as volume scales. Lifecycle covers turning raw prospect data into CRM-ready leads with explicit pass or fail gates instead of silent bad records.
How it compares
Deterministic CRM field mapper MCP, not a general Salesforce admin skill or LLM research tool.
Common Questions / FAQ
Who is apollo-salesforce-mapper for?
It is for builders and indie GTM operators who use Apollo for prospecting and Salesforce for pipeline tracking and want MCP-driven, non-LLM lead mapping.
When should I use apollo-salesforce-mapper?
Use it during Grow lifecycle work whenever you batch-map Apollo contacts to Salesforce Leads and need strict-fail validation before create or update operations.
How do I add apollo-salesforce-mapper to my agent?
Add the remote MCP endpoint https://cf-worker.selbyventurecap.workers.dev/mcp as a streamable-http server in Claude Code, Cursor, or another MCP client, then call its mapping tools from your sync workflow.