Toolkit / IT approval kit / Apollo

Apollo connector: IT approval one-pager

Apollo's MCP server can read and change data. The vendor's setup notes don't mention an admin step. This page covers what it can reach and change, how it signs in, who approves it and how to turn it off.

Download (.md) Print this page

Server URL

https://mcp.apollo.io/mcp Source: StackMCP listing, checked 2026-10-16

Access

Read + write

Source: docs.apollo.io, checked 2026-10-16

Sign-in

OAuth 2.0 (master API key / X-Api-Key for headless) Source: StackMCP listing, checked 2026-10-16

Admin approval

Not confirmed

Setup

Self-serve

No admin step in the vendor's setup notes. Source: docs.apollo.io, checked 2026-10-16

Credits

Some tools use credits

Source: docs.apollo.io, checked 2026-10-16

Plan

Free Source: knowledge.apollo.io, checked 2026-10-16

What data can it reach?

Apollo's docs list these tools for its MCP server:

• people/company search
• enrichment
• contacts & accounts CRUD
• sequences
• one-off email
• lists
• tasks
• analytics

• It works within your Apollo permissions, plan and credits. The assistant can only do what your Apollo account allows. Source: docs.apollo.io, checked 2026-10-22

What can it read, and what can it change?

Read + write Some Apollo MCP tools change data, not just read it.

Things it can do in your Apollo account:

• creates and updates contacts and accounts
• creates deals
• adds and removes contacts in sequences (enrollment)
• creates and updates sequences
• sends one-off emails
• creates and updates lists and adds/removes records
• creates, completes and skips tasks
• creates and applies labels
• creates custom objects
• connects data sources and imports records
• purchases sending domains and email accounts

Review each change before you approve it, especially anything that sends messages or edits records other people rely on.

Which actions should wait for a person's OK?

Have a person approve each change or purchase listed above before it runs. Every StackMCP recipe follows this rule: read freely, but create, change, send or buy only after you approve it.

• It can buy sending domains and email accounts for cold email. Have a person approve any purchase before it runs. Source: docs.apollo.io, checked 2026-10-22

Also check before you run anything that spends credits or quota (a usage limit). Credits or quota for this connector: Some tools use credits.

How does it sign in?

Sign-in method (from the StackMCP listing): OAuth 2.0 (master API key / X-Api-Key for headless)

• With OAuth, the assistant can only reach the data and actions of the Apollo user who connected it. Source: docs.apollo.io, checked 2026-10-22
• OAuth needs a browser. Clients with no browser, like a server, cron job or CI pipeline, use an Apollo API key instead. It has to be a master key. Source: docs.apollo.io, checked 2026-10-22
• Apollo says to treat a master key like a password: anyone who holds it can take any API action the workspace allows. Source: docs.apollo.io, checked 2026-10-22
• An API key isn't tied to the person who made it. Requests made with it act as the workspace's longest-standing active admin. Source: docs.apollo.io, checked 2026-10-22

Does an admin need to approve it?

What Apollo's docs confirm about admin controls:

• An admin must approve or enable the connectionNot confirmed
• Scopes or permissions can limit what it reachesYesSource: knowledge.apollo.io, checked 2026-10-16
• Individual tools can be turned offNot confirmed
• MCP activity shows in an audit logNot confirmed

How do we turn it off?

In Apollo

• To revoke OAuth access, go to the connected app or your account settings. To revoke an API key, regenerate or delete it in Apollo's developer dashboard. Source: docs.apollo.io, checked 2026-10-22

In the AI assistant

• In Claude, you can revoke access at any time. Disconnect the connector in Claude's settings, or in the tool's own security settings. Source: support.claude.com, checked 2026-10-22
• For other assistants, check that assistant's settings or ask your admin.

Does it use credits or quota?

Some tools use credits

Company search, company enrichment (single and bulk), company job postings, and people enrichment (single and bulk) use credits; people/contact search, CRM, sequence, email, task and analytics actions do not. Get conversation insights uses credits only if the conversation has AI insights.

Send this to IT

Copy this, fill in the parts in [brackets] and send it.

Subject: Request: connect Apollo to [your AI assistant] for my sales work

Hi [name],

I'd like to connect Apollo to [your AI assistant] using Apollo's official MCP connector. I want to use it for [task, for example call prep or pipeline review].

What I'm asking for:
- Approval to connect Apollo with OAuth as my own Apollo user, so it can only do what my Apollo user can do. I'm not asking for an API key, because Apollo's API key acts as the workspace's longest-standing active admin.
- Any admin step Apollo needs before I can connect.

How I'll use it:
- I'll approve each action that creates, changes, sends or buys something before it runs.
- I'll disconnect it if you ask, or when I stop using it.

Quick facts:
- Access: Read + write
- Sign-in: OAuth 2.0 (master API key / X-Api-Key for headless)
- Setup: Self-serve
- Credits: Some tools use credits

The facts and their sources: https://mcpforgtm.com/toolkit/it-approval/apollo

Thanks,
[your name]

Each fact links to its source: the tool vendor's docs, the AI assistant's docs or the StackMCP listing. Anything without a source says Not confirmed. Vendors change their connectors, so confirm anything important on the linked page. We last checked the quotes on this page (vendor docs and the Claude help article) on Oct 22, 2026, and the StackMCP listing facts on Oct 16, 2026.

All the facts on one page, with sources: Apollo MCP server. Setup steps: Connect Apollo.

Other one-pagers: HubSpot · Salesforce · Gong · Slack

Something out of date on this page? Report a correction, with a link to the vendor page that shows the right information.