# Clay MCP connector

The Clay connector brings the contact and company enrichment tools set up in your Clay workspace to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can find and enrich prospects inside their own Clay access.

Source: https://elaichi.ai/connectors/clay/

## Facts

| | |
| --- | --- |
| Application | Clay |
| Category | Sales Intelligence |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Clay builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@clay.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Clay is connected

- Find the head of sales at Acme and get a work email
- Enrich these five companies with headcount, funding and industry
- Which of my inbound leads are missing a job title?

## Connect Clay in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Clay.
2. Optionally set Share with, then press Connect.
3. Approve it in Clay. Clay's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Clay tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Clay MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Clay MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Clay MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Clay to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Clay tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Clay through Elaichi

### Build a researched list before the first touch

Sales development. Ask for companies that match your ideal profile and have Clay enrich each one with headcount, funding and the right decision maker, then start writing.

### Fill in a prospect before the call

Sales. Pull a company's size, tech stack and recent news from the enrichments your Clay workspace already runs, so you walk in knowing who you are talking to.

### Enrich a webinar list before the follow-up

Marketing. Run the attendee list through your Clay enrichments to add titles, company size and work emails before the nurture sequence goes out.

### Catch missing fields on inbound leads

Revenue operations. Find the job title, industry and company domain for leads that arrived half filled, using the enrichment steps your Clay workspace has set up.

### Find the right contact at a target partner

Partnerships. Ask Clay for the person who owns partnerships at a company, with a verified work email, instead of guessing from a website.

### Spot changes at an existing account

Customer success. Check whether a champion has changed jobs or an account has grown, using the people and company tools your Clay workspace already has.

## Elaichi vs Zapier MCP vs Composio for Clay

All three can connect Clay to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Clay tools | Allow or restrict single Clay tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Clay call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Clay to Claude?

Connect Clay in Elaichi first, where you sign in to Clay over OAuth and allow access, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi once, and from then on the Clay tools in your workspace are available in the conversation.

### Does Clay work with ChatGPT and Cursor as well as Claude?

Yes. Clay is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor or any other MCP client. The Elaichi Agent uses that same Clay connection too, so there is nothing to set up a second time.

### What can an AI agent actually do with my Clay data?

It can use whatever your Clay workspace has set up: finding people and companies, enriching a contact with a title, work email or company size, and running the custom functions your team has built. You ask in plain words, for example the decision maker at a named company, and it picks the right Clay step. Short, concrete asks work better than long sentences.

### Does connecting Clay give the AI my whole workspace?

No. The AI acts as the person who signed in to Clay, so it can only reach the tables, enrichments and functions that person can already reach in Clay. Elaichi can narrow that further for a team or a toolbox, and it can never widen it beyond what Clay itself allows.

### Can my team share one Clay connection?

Yes. One person connects Clay in Elaichi and shares it with a team, and nobody else ever handles a Clay credential. Each teammate still signs in to Elaichi as themselves, so every Clay lookup in the audit log carries the name of the person who asked for it.

### Can I stop an agent from changing things in Clay?

Yes. Restrictions in Elaichi apply per action, so you can allow finding and enriching people and companies in Clay while blocking anything that writes or removes. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

### What happens to a Clay connection when someone leaves?

Offboarding a person in Elaichi ends their access to Clay through every client at once. If they had shared a Clay connection with a team, it keeps working for everyone else. Disconnecting Clay once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.

### Does the Clay MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Clay is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Clay?

Yes. Both let Claude, ChatGPT or Cursor use Clay. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Clay call.

### How is Elaichi different from Composio for Clay?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Clay: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.