Apollo.io

Two different signals live in one connector: firmographic and role search for who to reach, and live job postings as a hiring signal for when to reach them. A company hiring for a role your product touches is often a stronger trigger than firmographic fit alone.

Does Apollo have an MCP server?

Yes. Apollo documents its own MCP server at https://mcp.apollo.io/mcp, with OAuth sign-in in a browser, or a master API key for clients that cannot open one. It covers search and enrichment, contacts, accounts and deals, lists, sequences, one-off emails, tasks, analytics and conversations, and it spends your Apollo credits like the app does. Tulina reaches Apollo through its own MCP server instead, on the same link that carries the rest of your stack.

How do you connect Apollo to Claude and ChatGPT?

Through Tulina's own MCP server, in three steps:

1. In Apollo, create an API key in the developer settings. Contacts, sequences, emails and conversations need a master key.
2. Paste it into Tulina's Apollo connector, for yourself or for the organisation. It is stored in the vault and never shown to the model. Without your own key, company and people search and enrichment run on a small free daily quota of the platform's shared key.
3. Add https://mcp.tulina.ai/mcp to Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.

Several Apollo keys can be connected as named accounts, and a request names the one it is for.

Tulina vs Apollo's official MCP server

Both reach the same Apollo data. They differ in how you sign in and in where credits come from.

If Apollo is the only system the model needs, or you work with deals, lists and tasks, Apollo's own server is the better choice. Tulina earns its place when a prospect list is one step in a longer piece of work.

What you can ask it

"Find VP Sales at SaaS companies in France with 50 to 200 people." The agent searches organizations on the firmographic filters, then searches people at those domains by title and seniority. Search results are obfuscated, so the agent enriches the shortlist, up to 10 people per call, before showing names and emails.

"Which of these companies is hiring a data engineer right now?" The agent reads each company's active job postings and returns the ones that match, which is the hiring signal that tells you when to reach them.

"Add the three people I picked to the Q4 sequence." The agent reads your connected mailboxes and send schedules, finds the sequence, then enrolls the contacts. A dry run first shows who would be enrolled, since this starts an automated campaign to real people.

Processes chain these steps without a prompt each time. Outbound from buying signals, Build a target list from a sentence and Turn signups into pipeline all run on Apollo. Apollo pairs with Hunter and FullEnrich when a verified email or phone is still missing, and with Lemlist for outreach.

What the Apollo connector can't do

• It does not manage deals, lists or tasks, which Apollo's own server does.
• Reveals of phone numbers and personal emails need your own Apollo key. They cost extra credits, and a phone number arrives minutes later and is collected with a separate call.
• Contacts, sequences, one-off emails and conversations always use your own key, and contacts need a master key. A standard key authenticates and then returns 403.
• A contact is not a person. Person search queries Apollo's shared database, while the contact tools only see people your team already saved.
• Bulk matching saves calls, not credits. Apollo bills per person.
• Updating a contact's list labels replaces its list membership instead of adding to it.
• When the free platform quota runs out, calls refuse and say it resets at midnight. Set your own key to lift it.