Sign in Book a demo
Back to Tools
Sales & CRM API Key
Build Your Agent View Apollo Documentation
apollo logo

Apollo MCP Tools for AI Agents

Let an agent search Apollo for target companies and people, enrich known contacts and organizations, and check remaining API capacity.

Available Tools

7 tools available in this integration

Apollo.EnrichOrganization

Turn a company domain into firmographics (industry, size, revenue, funding,

Apollo.EnrichPerson

Turn a known person into a verified profile with their current role and,

Apollo.GetApiUsage

Report per-endpoint rate limits and how many requests remain, so the agent

Apollo.GetOrganization

Turn a company domain into firmographics (industry, size, revenue, funding,

Apollo.GetPerson

Turn a known person into a verified profile with their current role and,

Apollo.SearchOrganizations

Find companies in Apollo's database that match a firmographic profile so a

Apollo.SearchPeople

Find people in Apollo's database by role and the firmographics of their

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find healthcare companies with 500+ employees and identify their heads of sales." Arcade picks the right Apollo tools without guessing whether to search organizations or people first.

Up to 100x fewer tokens

Apollo search and lookup results return focused company and person profiles by default, so the agent can qualify a market without loading unrelated records or full datasets.

Complete the workflow end to end

Search target companies, find relevant people, enrich their profiles, compare the results, and return a focused prospect list through one toolkit designed around the complete sales research task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Apollo

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Apollo, you can implement some of these policies:

Access when tools are listed for a user
  • Decide which tools an agent is allowed to see at all. A tool that is never listed cannot be called, whoever is asking.
Pre-execution before each tool call
  • Inspect the inputs a call is about to run with, and block it or send it for human approval when they fall outside what the agent should do unsupervised.
Post-execution after the tool returns
  • Redact personal phone numbers and email addresses from Apollo.EnrichPerson results before they reach the model, so an agent cannot expose direct contact details.
  • Strip personal phone numbers and email addresses from Apollo.SearchPeople results, leaving role and firmographic context without private contact data.
  • Redact revenue and funding fields from Apollo.EnrichOrganization results before the model sees them, so sensitive company financials stay out of agent context.

How to use Apollo with your agent

Connect Apollo to your MCP client with a shared API key, then try the tools from your agent. Follow the walkthrough to configure the client and run your first company or people search.

Your questions, answered

An Apollo MCP server exposes Apollo sales-intelligence capabilities as structured tools that an AI agent can call through the Model Context Protocol. Agents can search organizations and people, retrieve or enrich profiles, and check API usage.

Arcade provides the MCP server for Apollo rather than relying on an Apollo-hosted endpoint. Arcade adds authenticated tool execution, approval and redaction policies, credential brokering, and access from supported agents and frameworks.

Arcade agents can search organizations by firmographics, search people by role and company criteria, retrieve organization and person profiles, enrich known companies or contacts, and report per-endpoint API usage and remaining requests. These actions are read-only.

Apollo access uses a shared API key or secret configured once for the integration. The key determines which Apollo data and endpoints the agent can reach; there is no separate OAuth scope set for each user in this setup.

No. Users do not each connect their own Apollo account. One shared Apollo credential is configured once, brokered by Arcade, and used for the connected workflows.

Yes. Contextual Access policies can require human approval before an Apollo call, hide Apollo actions from an agent, or redact fields from responses. The Apollo actions exposed here are read-only, so they do not create, update, or delete Apollo records.

Arcade proxies Apollo API calls and does not persist your Apollo content as part of normal tool execution. The shared credential is brokered and stored encrypted at rest, and the model never receives it.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works with Arcade Apollo, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade continues using the shared Apollo credential while it remains valid. If the key is revoked, rotated, or otherwise stops working, Apollo calls stop until the credential is reconnected or updated.

Apollo rate limits apply to calls made through Arcade. You can check per-endpoint limits and the number of requests remaining, but the exact quota depends on the configured Apollo credential and endpoint.

Ready to actually ship your agent?

Connect your agent to Apollo with a shared API key, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Apollo Quickstart