Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
dev.workers.selbyventurecap.cf-worker avatar

Apollo Salesforce Mapper MCP

dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper is a MCP server that maps Apollo leads into Salesforce with strict required-field checks and PASS/REPAIR/FAIL verdicts.

About

The Apollo–Salesforce Lead mapper is a remote MCP server for developers and small revenue teams who sync outbound lists from Apollo into Salesforce without handing field mapping to a model. It applies strict-fail rules on required Lead attributes, then labels each record with a PASS, REPAIR, or FAIL verdict so you can quarantine bad rows, patch fixable gaps, and only push clean leads. That fits operators who automate CRM updates from Claude Code or Cursor but still want deterministic, auditable transforms instead of probabilistic JSON. Install it when you are wiring growth stack integrations, not when you need generic chat or open-ended research. The worker exposes streamable HTTP MCP and ships as version 2.0.0 with a narrow, integration-first contract.

  • 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

Apollo Salesforce Mapper MCP by the numbers

  • Exposes 1 verified tools (MCP introspection)
  • Data as of Aug 10, 2026 (Skillselion catalog sync)
terminal
claude mcp add --transport http apollo-salesforce-mapper https://cf-worker.selbyventurecap.workers.dev/mcp

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
TransportHTTP
AuthNone
Tools1

What it does

Map Apollo prospect exports into Salesforce Lead fields with deterministic validation before your CRM sync jobs run.

Who is it for?

Best when you're piping Apollo into Salesforce via an MCP-aware agent and want rule-based mapping, not LLM guesswork.

Skip if: Skip if you need bi-directional Salesforce sync, custom object mapping beyond Leads, or AI-generated enrichment narratives.

What you get

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

By the numbers

  • Server version 2.0.0
  • No LLM in the mapping pipeline
  • Three verdict states: PASS, REPAIR, FAIL

Tools 1

Public tool metadata - what this server can do for an agent.

apollo_to_salesforce_lead41 params

Maps an Apollo contact payload to a Salesforce Lead object. Accepts the full Apollo CSV export column set. Strict-fail if FirstName, LastName, or Phone cannot be resolved. All other Salesforce fields are populated when source data is present, silently omitted otherwise. Returns a Deterministic Receipt (task_id, verdict, confidence, diff[]) embedded in every non-FAIL response.

  • full_namestringFull name — must have ≥2 whitespace-separated tokens. Use this OR provide first_name + last_name. Example: 'Jane Doe'
  • first_namestringFirst name (Apollo split export). Use with last_name instead of full_name.
  • last_namestringLast name (Apollo split export). Use with first_name instead of full_name.
  • cellstringPrimary phone (legacy key). Accepts E.164, 10-digit US, formatted strings.
  • phonestringApollo 'Phone' column — alternate primary phone key.
  • mobile_phonestringApollo 'Mobile Phone' column. Maps to MobilePhone if a primary phone exists.
  • work_phonestringApollo 'Work Phone' column — lowest-priority fallback.
  • prop_addrstringFull property address string (legacy v1 key) → PropertyAddress.
  • streetstringStreet address → Street.
  • citystringCity → City.
  • person_citystringApollo 'Person City' column → City.
  • statestringState / province → State.
  • person_statestringApollo 'Person State' column → State.
  • postal_codestringZIP / postal code → PostalCode.
  • zipstringAlternate ZIP key → PostalCode.
  • person_postal_codestringApollo 'Person Postal Code' → PostalCode.
  • countrystringCountry → Country.
  • person_countrystringApollo 'Person Country' → Country.
  • emailstringContact email → Email.
  • companystringCompany name → Company.
  • organizationstringApollo 'Organization' column → Company.
  • account_namestringApollo 'Account Name' column → Company.
  • titlestringJob title → Title.
  • job_titlestringApollo 'Job Title' column → Title.
  • senioritystringApollo seniority level → Description.
  • departmentsstringApollo departments string → Description.
  • linkedin_urlstringLinkedIn profile URL → LinkedIn__c.
  • linkedinstringAlternate LinkedIn key → LinkedIn__c.
  • websitestringCompany website → Website.
  • company_websitestringApollo 'Company Website' → Website.
  • twitter_urlstringTwitter/X URL → Twitter__c.
  • industrystringIndustry → Industry.
  • annual_revenuestringAnnual revenue string, e.g. '$1.2M', '500000' → AnnualRevenue (number).
  • estimated_annual_revenuestringApollo estimated revenue → AnnualRevenue.
  • number_of_employeesstring | numberEmployee count or range (e.g. '500-1000') → NumberOfEmployees.
  • num_employeesstring | numberAlternate employees key.
  • employeesstring | numberAlternate employees key.
  • lead_sourcestringLead source string → LeadSource (mapped to Salesforce picklist values).
  • sourcestringApollo 'Source' column → LeadSource.
  • keywordsstringApollo keywords/tags → Description.
  • headlinestringLinkedIn headline captured by Apollo → Description.

Recommended MCP Servers

How it compares

Deterministic CRM field mapper MCP, not a general Salesforce admin skill or LLM research tool.

FAQ

Who is apollo-salesforce-mapper for?

It is for developers and 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.

Communicationlifecycle

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.