Apollo.io
Prospecting and data enrichmentProspect database plus email sequences, dialer and CRM enrichment in one tool. Apollo MCP connects it to MCP client apps such as ChatGPT, Claude and Cursor, using your Apollo credits for enrichment.
Independent review. Unpaid; no partnership with Clay. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Spreadsheet-style enrichment that pulls from many data providers and AI research steps (Claygent) to build target lists. Its MCP server lets AI assistants and IDEs run Clay's find-and-enrich tools for a signed-in user.
Judgment, not a score. Documentation checked 2026-10-18.
Connections: MCP connections · APIs · Portability and vendor lock-in.
Free includes 500 actions and 100 data credits per month, up to 200 rows per table and unlimited seats. Launch starts at $185/month monthly or $167/month billed annually; Growth starts at $495/month monthly or $446/month billed annually. Paid totals vary with action and credit selections. Confirm currency, tax and selected capacity at checkout. Checked 2026-10-18. source ↗
Clay documents a CLI/plugin for Claude Code, Codex and Cursor, plus API searches and routines. Existing-table queries are Enterprise-only; building Workflows through the developer platform is marked Alpha. These interfaces are distinct from HTTP API enrichment inside a table, which the pricing comparison limits to Growth and Enterprise. source ↗
CSV imports can append or replace data and can trigger enrichment immediately. Review the import and run settings first. For HTTP integrations, use saved credentials rather than entering secrets directly into visible table configuration. source ↗
How Clay connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Official Clay plugin/CLI documentation names Claude Code. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Clay named integration docs ↗Clay MCP / connector evidence ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Clay publishes an API, but this pairing still needs network, authentication and execution-scope checks. Clay API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Clay is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Clay's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Clay file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Official Clay plugin/CLI documentation names Codex. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Clay named integration docs ↗Clay MCP / connector evidence ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Clay publishes an API, but this pairing still needs network, authentication and execution-scope checks. Clay API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Clay is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Clay's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Clay file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Clay has an official MCP server and Google Antigravity supports MCP, but Clay's docs don't name this pairing. Auth setup may differ. Clay MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Clay publishes an API, but this pairing still needs network, authentication and execution-scope checks. Clay API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Clay is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Clay's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Clay file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ - hosted MCP with OAuth dynamic client registration and PKCE; workspace membership and administrator client permissions apply. |
| API / CLI | Yes | Official docs ↗ - API and coding-agent CLI for searches and routines; querying existing Tables is Enterprise-only. HTTP API enrichment is a separate Growth/Enterprise feature. |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ - CSV import can append or replace table data. Choose whether to run enrichment immediately; runs may consume credits. |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Sales, CRM & outreach Enrichment
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
No long-form review yet. Verdict is based on research, not hands-on testing.
Prospect database plus email sequences, dialer and CRM enrichment in one tool. Apollo MCP connects it to MCP client apps such as ChatGPT, Claude and Cursor, using your Apollo credits for enrichment.
CRM with free tools for up to two users and 1,000 contacts. An official remote MCP server lets authorized agents read and update supported CRM records; available tools depend on the subscription, permissions and account settings.