Apollo MCP

Live

OAUTH 2.0

CRM & SALES

Marketing

Connect to Apollo MCP to search B2B contacts, enrich people and organizations, manage CRM records, and enroll prospects in sequences.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Apollo MCP
agent · Acme Q3
Run
Apollo Accounts Bulk Create in Apollo MCP
S
apollomcp_apollo_accounts_bulk_create
85ms
Apollo MCP agent
Create multiple accounts (companies) in a single call by passing an array of account objects. no deduplication is applie.
Sources: Apollo MCP
apollomcpmcp
1 tool call
18:29
Message Claude...

Tools your agent reaches for on Apollo, scoped per user.

CALL ANY TOOL
Search, enrich, and sequence B2B contacts and accounts, billed to the requesting user's seat.
apollomcp_apollo_accounts_bulk_create
Create multiple accounts (companies) in a single call by pas
Create multiple accounts (companies) in a single call by passing an array of account objects. no deduplication is applied — each object becomes a new record even if it matches an existing account by name or domain; review the array carefully before submitting.
Parameters
Name
Type
Required
Description
accounts
array
Required
Array of account objects to create. Each object accepts the same fields as the single Create Account endpoint: name, domain, phone, raw_address, typed_custom_fields.
_conversation_ref
string
Optional
Short random token generated on your first call in a conversation; reuse the exact same value on every subsequent call to group related tool calls for analytics.
_rationale
string
Optional
Describe the user's intent and why this tool was selected in general terms only; do not include specific field values, names, emails, or other data.
apollomcp_apollo_accounts_create
Add a new account (company) to your team's apollo database.
apollomcp_apollo_accounts_update
Update an existing account (company) in your team's apollo d
apollomcp_apollo_analytics_sync_report
Query apollo's sales analytics data with flexible filtering,
apollomcp_apollo_contacts_bulk_create
Create multiple contacts in a single call by passing an arra
apollomcp_apollo_contacts_create
Create a new contact in your team's apollo account. apollo a
apollomcp_apollo_contacts_search
Search for contacts that have been added to your team's apol
apollomcp_apollo_contacts_update
Update an existing contact in your team's apollo account. re
apollomcp_apollo_email_accounts_index
Retrieve all linked email inboxes (mailboxes) for your team'
apollomcp_apollo_emailer_campaigns_add_contact_ids
Add contacts to existing sequences in your team's apollo acc
apollomcp_apollo_emailer_campaigns_approve
Activate (turn on) an existing sequence so that contacts enr
apollomcp_apollo_emailer_campaigns_remove_or_stop_contact_ids
Remove or stop contacts from one or more existing sequences
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="apollomcp")

mcp = MultiServerMCPClient({
"apollomcp": {
"url": "https://mcp.scalekit.com/apollomcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "apollomcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/apollomcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "apollomcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/apollomcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="apollomcp")
# Connect to MCP at https://mcp.scalekit.com/apollomcp
# Pass: Authorization: Bearer + token
Try these prompts
Copy any prompt into your agent. Each maps directly to a Apollo tool. Click to copy, paste into your agent, done.
Get started
Copy the prompt
Copied
Use the Profile endpoint to get the user’s profile information (name, email, title, id)?
Copy the prompt
Copied
Retrieve credit usage stats for the authenticated team — credits used, remaining, and reset windows for enrichment/peopl?
Advanced
Copy the prompt
Copied
Edit an existing task in place — change its title, note, priority, due date, assignee, or the message body (subject / bo?
Copy the prompt
Copied
Skip a single task without performing it?
SEE HOW AUTH WORKS
Your users connect once. Their Apollo credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Apollo MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Apollo MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Apollo MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Apollo MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Apollo as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Apollo OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Apollo?
Yes. Pass a tool name filter to listScopedTools so the marketing agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Apollo.

What happens when a user revokes Apollo access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent enroll contacts into Apollo sequences automatically?
Yes. Sequence enrollment runs with the authorizing user's Apollo seat and sender accounts. Adds, updates, and bulk creates all log that user's identity, keeping outbound compliant.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""apollomcp"": {
""url"": ""https://mcp.scalekit.com/apollomcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.apollomcp]
url = ""https://mcp.scalekit.com/apollomcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""apollomcp"": {
""url"": ""https://mcp.scalekit.com/apollomcp"",
""type"": ""http""
}
}
}