Provider REST API

Sales

Connect Claude to Apollo

Prospect Apollo's B2B database and manage the workspace's own contacts, accounts and sequences. Toolspoke puts 11 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connection
Provider REST API
Authentication
API key
Actions exposed
11
Cost per call (typical)
1 credit
Adapter
Maintained by Toolspoke

Connected in three steps

  1. 1

    Install Apollo

    Open the marketplace in your workspace, add Apollo to the project your agents work in, and it appears on the gateway immediately.

  2. 2

    Connect the credential

    Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.

  3. 3

    Point your agent at the gateway

    Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json
{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Apollo shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code

Run it in your project, then /mcp to sign in

claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop

Settings, then Connectors, then Add custom connector

https://toolspoke.com/mcp
Cursor

~/.cursor/mcp.json, or .cursor/mcp.json for one project

{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex

~/.codex/config.toml

[mcp_servers.toolspoke]
url = "https://toolspoke.com/mcp"
VS Code

.vscode/mcp.json, or the MCP: Add Server command

{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Apollo asks for

API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

API keyRequired
Apollo → Settings → Integrations → API → API keys. The key belongs to the workspace, not to you, and calls made with it are attributed to the workspace's earliest active admin. Sequences, accounts and the user list need a key created as a master key; the searches, the enrichments and the contact operations work with an ordinary one.
Apollo API key

What Claude can do in Apollo

11 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads
6Reads
Writes
2Writes
Destructive
3Destructive

Reads

6

Fetches data and changes nothing.

  • search_people

    Search Apollo's database of people by job title, seniority, location and employer. This is the free half of prospecting and the one to start from: it costs no credits and, by Apollo's own design, returns no email addresses and no phone numbers - names, titles, employers and Apollo person ids. Take an id from here to enrich_person when you actually need contact details, which is the call that costs credits. Filters combine with AND across fields and OR within a field, so two titles widen the search and a title plus a location narrows it.

  • list_contacts

    Search the contacts already saved in this Apollo workspace - the people the account has actually taken an interest in, as opposed to the whole database that search_people reaches. Costs no credits. Returns the stored record including any email address and phone number already revealed for that person, which is why the response is never written to the audit log.

  • list_sequences

    List the outbound sequences (Apollo calls them emailer campaigns) this workspace has defined, with their names, ids and status. Costs no credits. This is the workspace's own campaign configuration rather than anybody's data, and it is a read only: this connector deliberately offers no way to add a person to a sequence, because that puts real mail in front of a real prospect. Needs a master key - an ordinary key is refused with a 403.

  • list_accounts

    Search the accounts saved in this Apollo workspace - the companies the account is working, as opposed to the whole database that search_organizations reaches. Costs no credits, which is the practical reason to try this before paying for an organization search: a company already in the workspace is here. Needs a master key or an explicitly scoped one.

  • list_users

    List the people on this Apollo workspace's own team, with their ids, names and email addresses. Call it to turn a colleague's name into the Apollo user id an owner field takes, and to see who a write made with this key will be attributed to - the key acts as the workspace's earliest active admin rather than as whoever installed it. These are the caller's own colleagues, not prospects. Costs no credits; needs a master key.

  • check_api_key

    Confirm the API key works. Returns Apollo's two health flags and nothing else - no record, no person, no company. This is the connection check precisely because it is the one read in the connector guaranteed to cost nothing: every other candidate either spends a credit or needs a master key, and an install that tested itself by billing the account would be the wrong kind of surprise.

Writes

2

Creates or updates something on the other side.

  • create_contact

    Save a person as a contact in this Apollo workspace. Costs no credits - creating a record is free, and it is finding the person's details that is billed. This does not email anybody and does not add them to a sequence; it only files the record, which is why it is a write. Apollo does not deduplicate by default, so set run_dedupe or check list_contacts first when the person may already be there.

  • update_contact

    Change fields on a contact already in this workspace. Only the fields you send are touched. Costs no credits, reaches nobody outside the workspace, and cannot delete the contact - moving somebody's stage or correcting a title is reversible, which is why this is a write. Get the contact id from list_contacts.

Destructive

3

Deletes or permanently alters something. Worth granting on purpose.

  • enrich_person

    Look one person up in Apollo's database and return what Apollo knows about them, including a work email address. THIS SPENDS CREDITS: Apollo charges one credit whenever it finds demographics or an email address, and it is classified destructive for that reason rather than because it changes anything - a write grant does not reach it, and spending somebody's balance should be a decision, not a side effect of a search. Give whatever you have: an Apollo person id, a LinkedIn URL, an email address, or a name together with the employer's domain. Set reveal_personal_emails only when a personal address is actually wanted; a work address comes back without it. Mobile numbers are not offered here at all - Apollo returns them asynchronously to a webhook this gateway does not host, so asking for one would spend eight credits and deliver nothing.

  • search_organizations

    Search Apollo's database of companies by name, headcount, location and the technologies they run. THIS SPENDS CREDITS: Apollo charges one credit for every page of results, up to 100 companies a page, which makes it the one search in this connector that is not free - ask for a large per_page and page through deliberately rather than crawling. It is classified destructive for that reason alone; the response is firmographic company data and contains no person's contact details. Take an organization id from here into search_people to find the people at a company you just found.

  • enrich_organization

    Return Apollo's full profile of one company - headcount, industry, funding, technologies, address and social links - from its web domain, website or LinkedIn URL. THIS SPENDS CREDITS: one credit per company, which is why it is classified destructive rather than as the plain read it otherwise is. The response is company data, not a person's. Give exactly one of domain, website or linkedin_url; adding `name` helps Apollo pick the right company when a domain is ambiguous.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else
The 11 actions above are the whole of it. A call to any other name is refused before it reaches Apollo rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential
Toolspoke holds no access to Apollo of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Apollo
Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Apollo. An agent has to ask.
It does not smooth over provider limits
Toolspoke does not retry, queue or back off around Apollo's own rate limits. A call that Apollo refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Apollo?

11 named actions: 6 that only read, 2 that write and 3 that delete or permanently alter something. They include search_people, enrich_person and search_organizations. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Apollo connector need?

API key. The connector asks for api key. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Apollo connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 11 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Apollo connector not do?

The 11 actions above are the whole of it. A call to any other name is refused before it reaches Apollo rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Apollo of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Apollo. An agent has to ask. Toolspoke does not retry, queue or back off around Apollo's own rate limits. A call that Apollo refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Apollo's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Apollo?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.