apollo-salesforce-mapper
Server Details
Apollo->Salesforce Lead mapper. No LLM. Strict-fail required fields. PASS/REPAIR/FAIL verdict.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as mapping Apollo contact data to Salesforce Leads, making it distinct by default.
The single tool name 'apollo_to_salesforce_lead' follows a clear and consistent pattern, using snake_case and descriptive terms that indicate the source (Apollo), target (Salesforce), and object type (Lead). There are no other tools to compare against, so consistency is inherently perfect.
A single tool is too few for the apparent scope of mapping between Apollo and Salesforce, which typically involves multiple operations such as creating, updating, deleting, or querying leads. This minimal set feels thin and incomplete for the domain, limiting functionality.
The tool surface is severely incomplete for the domain of Apollo-Salesforce integration. It only provides one-way mapping from Apollo to Salesforce Leads, with no tools for reverse mapping, handling other Salesforce objects (e.g., Contacts, Accounts), or performing CRUD operations, leading to significant gaps that will cause agent failures.
Available Tools
1 toolapollo_to_salesforce_leadApollo → Salesforce Lead MapperInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | Alternate ZIP key → PostalCode. | |
| cell | No | Primary phone (legacy key). Accepts E.164, 10-digit US, formatted strings. | |
| city | No | City → City. | |
| No | Contact email → Email. | ||
| phone | No | Apollo 'Phone' column — alternate primary phone key. | |
| state | No | State / province → State. | |
| title | No | Job title → Title. | |
| source | No | Apollo 'Source' column → LeadSource. | |
| street | No | Street address → Street. | |
| company | No | Company name → Company. | |
| country | No | Country → Country. | |
| website | No | Company website → Website. | |
| headline | No | LinkedIn headline captured by Apollo → Description. | |
| industry | No | Industry → Industry. | |
| keywords | No | Apollo keywords/tags → Description. | |
| No | Alternate LinkedIn key → LinkedIn__c. | ||
| employees | No | Alternate employees key. | |
| full_name | No | Full name — must have ≥2 whitespace-separated tokens. Use this OR provide first_name + last_name. Example: 'Jane Doe' | |
| job_title | No | Apollo 'Job Title' column → Title. | |
| last_name | No | Last name (Apollo split export). Use with first_name instead of full_name. | |
| prop_addr | No | Full property address string (legacy v1 key) → PropertyAddress. | |
| seniority | No | Apollo seniority level → Description. | |
| first_name | No | First name (Apollo split export). Use with last_name instead of full_name. | |
| work_phone | No | Apollo 'Work Phone' column — lowest-priority fallback. | |
| departments | No | Apollo departments string → Description. | |
| lead_source | No | Lead source string → LeadSource (mapped to Salesforce picklist values). | |
| person_city | No | Apollo 'Person City' column → City. | |
| postal_code | No | ZIP / postal code → PostalCode. | |
| twitter_url | No | Twitter/X URL → Twitter__c. | |
| account_name | No | Apollo 'Account Name' column → Company. | |
| linkedin_url | No | LinkedIn profile URL → LinkedIn__c. | |
| mobile_phone | No | Apollo 'Mobile Phone' column. Maps to MobilePhone if a primary phone exists. | |
| organization | No | Apollo 'Organization' column → Company. | |
| person_state | No | Apollo 'Person State' column → State. | |
| num_employees | No | Alternate employees key. | |
| annual_revenue | No | Annual revenue string, e.g. '$1.2M', '500000' → AnnualRevenue (number). | |
| person_country | No | Apollo 'Person Country' → Country. | |
| company_website | No | Apollo 'Company Website' → Website. | |
| person_postal_code | No | Apollo 'Person Postal Code' → PostalCode. | |
| number_of_employees | No | Employee count or range (e.g. '500-1000') → NumberOfEmployees. | |
| estimated_annual_revenue | No | Apollo estimated revenue → AnnualRevenue. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!