Apollo MCP | OAuth Apollo connector for AI agents

CALL ANY TOOL

Search prospects, enrich contacts, manage sequences, and update accounts. Same toolkit, every framework, no auth plumbing.

apollo_mixed_people_api_search

Search people

Search Apollo's B2B people database with filters for title, company, location, industry, and seniority.

Parameters

Name

Type

Required

Description

q_keywords

string

Optional

Free text keywords to match

person_titles

array

Optional

Array of job titles to filter by

person_seniorities

array

Optional

Seniority levels: owner, founder, c_suite, partner, vp, head, director, manager

organization_num_employees_ranges

array

Optional

Employee count ranges

page

integer

Optional

Pagination page (default 1)

apollo_mixed_companies_search

Search companies

apollo_people_match

Enrich person

apollo_organizations_enrich

Enrich organization

apollo_contacts_create

Create contact

apollo_emailer_campaigns_add_contact_ids

Add to sequence

apollo_emailer_campaigns_search

Search sequences

Build your Agent

Drop the toolkit in, point it at the user, and your agent can search Apollo prospects, enrich contacts, and run sequences from the first run.

Copied

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apollo"], toolNames: ["apollo_mixed_people_api_search", "apollo_people_match", "apollo_emailer_campaigns_add_contact_ids"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

Copied

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apollo"], toolNames: ["apollo_mixed_people_api_search", "apollo_people_match", "apollo_emailer_campaigns_add_contact_ids"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["apollo"], toolNames: ["apollo_mixed_people_api_search", "apollo_people_match", "apollo_emailer_campaigns_add_contact_ids"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

Copied

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/apollo",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start building targeted prospect lists from Apollo.

Search & build lists

Copy the prompt

Copied

Find VP Engineering leads at Series B SaaS companies under 200 employees.

Copy the prompt

Copied

Search for CFOs at fintech companies in EMEA.

Copy the prompt

Copied

List all Heads of Sales at companies hiring SDRs right now.

Copy the prompt

Copied

Find Marketing Directors at companies using Snowflake.

Enrich & qualify

Copy the prompt

Copied

Enrich [email] with full firmographic data.

Copy the prompt

Copied

Match [LinkedIn URL] to an Apollo profile.

Copy the prompt

Copied

Get the funding stage and tech stack for [company domain].

Copy the prompt

Copied

Find verified emails for the top 10 leads at [company].

Sequence & outreach

Copy the prompt

Copied

Add these 50 leads to the [sequence name] campaign.

Copy the prompt

Copied

List all active sequences I own.

Copy the prompt

Copied

Pause the [sequence name] sequence for [contact list].

Copy the prompt

Copied

Show me reply rates across my sequences this month.

SEE HOW AUTH WORKS

Users authorize Apollo once. Their workspace credentials stay vaulted, every call is checked, and every action is logged.

1

Authorize

Your user connects

Apollo

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

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

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

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

Same per-user auth pattern across other prospecting agents and MCP connectors. Working code, live demos, fork what fits.

SALES

Outbound prospecting agent

Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.

Apollo

View agent

GTM

CRM AI agent

Log calls, update opportunity stages, and surface stalled deals across HubSpot or Salesforce. No manual data entry.

HubSpot

Salesforce

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Prospecting logged under the integration

A shared Apollo token looks fine in a demo. In production, every contact or account retrieved looks like it came from a service account. Audit logs break. Per-rep scoping breaks. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared bot token
token = "sk_apollo_shared_xxx"
audit → bot_service_account
rep_filter → broken

// scalekit · per-user
token = resolve(user_id)
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Apollo today. HubSpot, Salesforce, Attio 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 2.0 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 prospecting 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. Use the sequence enrollment tool with a contact ID list and a sender account. Sequence ownership and seat licensing are respected. Adds and pauses are logged with the authorizing user's identity.

Apollo

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