Skip to main content
Glama
borgels

mcp-server-apollo

by borgels

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for HTTP transport
MCP_HTTP_HOSTNoHost for HTTP transport
APOLLO_API_KEYYesApollo.io API key (required)
MCP_HTTP_TOKENNoStatic bearer token for HTTP transport
APOLLO_AUDIT_LOGNoPath to JSONL audit log file
APOLLO_TIMEOUT_MSNoTimeout in milliseconds for API calls
MCP_MAX_BODY_BYTESNoMaximum body size in bytes
MCP_ALLOWED_ORIGINSNoAllowed origins for CORS

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
apollo_search_capabilitiesA

Search the Apollo MCP server capabilities and examples. Use this first when deciding which Apollo tool to call.

apollo_companies_searchA

Discover companies via Apollo by keyword tags, name, location (include/exclude), employee-count ranges, revenue range, domains, or technology stack. The response preserves Apollo's split between organizations (net-new) and accounts (already saved to your Apollo team, incl. CRM linkage) — use it to dedupe against your CRM — and passes pagination (page/per_page/total_entries/total_pages) through unchanged. COSTS 1 CREDIT per request (page) that returns results — confirm total credit cost with the user before running multi-page batches. Search records are slim; use apollo_org_enrich for revenue/industry/technology details.

apollo_people_searchA

Find people via Apollo by title, seniority, location, employer domain/id, or employer size. FREE (no credits) but requires a MASTER Apollo API key. Results are intentionally slim: last names are obfuscated ("Hu***n") and NO email addresses or phone numbers are included — do not loop searching for contact data; pass the returned person id to apollo_person_enrich instead.

apollo_person_enrichA

Match one person via Apollo and return their full profile (employment history, employer, departments, seniority). CONSUMES CREDITS when a record is enriched; setting revealPersonalEmails or revealPhoneNumber costs extra per your Apollo plan (typically ~1 credit per email, ~8 per mobile) — confirm with the user first. Phone numbers are NOT in the synchronous response: Apollo delivers them asynchronously to webhookUrl (required for phone reveals); poll apollo_webhook_result with the returned request_id if the callback is missed. Personal emails are not revealed for people in GDPR regions; you are the data controller for retrieved personal data.

apollo_people_bulk_enrichA

Enrich up to 100 people via Apollo in one call. Chunks into bulk_match calls of 10, fans out with bounded concurrency, retries HTTP 429, and isolates per-item failures. Returns { total, succeeded, failed, creditsConsumed, requestIds, results[] } with results in input order. CONSUMES CREDITS per enriched record and reveal flags apply to EVERY person — confirm total credit cost with the user first. Apollo rate-limits bulk_match hard (documented 20/min). revealPhoneNumber requires webhookUrl. Emits MCP progress notifications when the client sends a progressToken.

apollo_org_enrichA

Fetch full firmographics for one company via Apollo: industry, keywords, employee count, revenue, funding events, technology stack (current_technologies / technology_names), department headcounts, and headcount growth rates. Provide at least one of domain, name, website, or linkedinUrl. Consumes 1 credit when a record is enriched. For Danish companies prefer the Lassox MCP (authoritative CVR registry data); use this for non-DK companies or Apollo-specific fields like technology stack.

apollo_webhook_resultA

Fetch the result of an asynchronous Apollo enrichment (phone-number reveal or waterfall) by request_id, in case the webhook callback was missed. Free (no credits); results are kept for 30 days. A 404 with retry_after_seconds means the result is not ready yet — wait before retrying.

apollo_credit_usageA

Report per-endpoint Apollo API usage against the minute/hour/day rate limits, plus the most recent rate-limit headers observed. Use before large batches to check headroom, and to answer "how much have we used?". Requires a master API key; consumes no credits. Note: Apollo exposes no API for the remaining credit balance — that is only visible in the Apollo UI (Settings > Billing and credits).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/borgels/mcp-server-apollo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server