Connect Apollo to Claude Code

Prospect Apollo's B2B database and manage the workspace's own contacts, accounts and sequences. Add Toolspoke to Claude Code once and it can use 11 Apollo actions. Your Apollo credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

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

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

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Apollo and connect it

    Add Apollo to a project in your Toolspoke workspace.

    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 key
    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.
  3. Choose what Claude Code may do

    All 11 actions start on. Switch off any of the 5 actions that change something in Apollo, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Apollo actions that only read, so they are safe to try first.

  • Search Apollo's database of people by job title, seniority, location and employer
  • List the people on this Apollo workspace's own team, with their ids, names and email addresses
  • Confirm the API key works

What Claude Code can do in Apollo

6 actions read, 2 write and 3 delete or permanently change something.

Reads

  • 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

  • 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.

Deletes or permanently changes

  • 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.

Apollo in Claude Code: questions

Does Claude Code see my Apollo credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Apollo?

Yes. Each of the 11 actions can be switched off for a project. Turn off the 5 that change something and Claude Code can only read.

Will 11 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Apollo action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Apollo call does not run in a sandbox, so it bills nothing.

Apollo in your other apps

More sales toolkits for Claude Code

Try Apollo in Claude Code

Free to start, and tool calls cost nothing on any plan.