Skip to main content
Glama
lkm1developer

Apollo.io MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTH_SERVER_URLNoURL pointing to your API key verification endpoint (for authentication)
APOLLO_IO_API_KEYYesYour Apollo.io API access token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
people_enrichmentC

Use the People Enrichment endpoint to enrich data for 1 person

organization_enrichmentC

Use the Organization Enrichment endpoint to enrich data for 1 company

people_searchD

Use the People Search endpoint to find people

organization_searchC

Use the Organization Search endpoint to find organizations

organization_job_postingsC

Use the Organization Job Postings endpoint to find job postings for a specific organization

get_person_emailC

Get email address for a person using their Apollo ID

employees_of_companyC

Find employees of a company using company name or website/LinkedIn URL

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some potential overlap between organization_search and organization_enrichment, as both involve company data retrieval. However, their descriptions clarify that search is for finding organizations while enrichment is for augmenting data on a known company, which helps mitigate confusion. The other tools target clearly different resources like employees, emails, job postings, and people.

Naming Consistency4/5

The naming follows a consistent snake_case pattern throughout, which is good. However, there is a minor inconsistency: most tools use a verb_noun format (e.g., organization_search, people_enrichment), but employees_of_company uses a noun_of_noun structure, deviating slightly from the pattern. This does not severely impact readability but is a noticeable deviation.

Tool Count5/5

With 7 tools, the count is well-scoped for a sales intelligence or recruitment domain, covering key operations like searching and enriching data for both organizations and people. Each tool appears to earn its place without feeling excessive or sparse, aligning well with the server's apparent purpose of data enrichment and lookup.

Completeness4/5

The tool set provides solid coverage for core workflows in the domain, including search and enrichment for both organizations and people, plus specific functions like finding employees and emails. A minor gap is the lack of update or delete operations, but this is reasonable for a read-heavy enrichment server. The surface supports common agent tasks without obvious dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues