Clay MCP connector
The Clay connector brings the contact and company enrichment tools set up in your Clay workspace to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can find and enrich prospects inside their own Clay access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Find the head of sales at Acme and get a work email
Working in Clay with Elaichi
-
Looked in Clay
How to connect Clay to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Clay MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Clay MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Clay MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Clay MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Clay to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Clay through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Clay is logged.
-
Sales development
Build a researched list before the first touch
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.
-
Sales
Fill in a prospect before the call
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.
-
Marketing
Enrich a webinar list before the follow-up
Run the attendee list through your Clay enrichments to add titles, company size and work emails before the nurture sequence goes out.
-
Revenue operations
Catch missing fields on inbound leads
Find the job title, industry and company domain for leads that arrived half filled, using the enrichment steps your Clay workspace has set up.
-
Partnerships
Find the right contact at a target partner
Ask Clay for the person who owns partnerships at a company, with a verified work email, instead of guessing from a website.
-
Customer success
Spot changes at an existing account
Check whether a champion has changed jobs or an account has grown, using the people and company tools your Clay workspace already has.
Try asking
- “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?”
What connecting Clay gets you
5 screens from Elaichi, each doing one job for your Clay account.
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Clay for a prospect in plain words.
Three starter prompts return live contacts and companies from your Clay workspace.
Copy the endpoint
AI apps
Clay works in every client through one endpoint.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Toolboxes
Each team gets its own Clay toolbox.
Sales development, marketing and operations each see only the Clay tools scoped to them.
Shared connections
Share a Clay connection, never a credential.
One person connects Clay, teammates enrich through it without ever seeing an API key.
Audit log
Every Clay lookup is on the record.
When, who, what happened and which contact or company, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Clay digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
Clay
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Clay
Queued
Workflows
A schedule enriches new leads before anyone asks.
New Clay records are fetched, grouped and drafted into a digest a person approves.
Clay health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales development 34%
Outbound EMEA 27%
Marketing 21%
RevOps 18%
Collections and dashboards
Clay health, measured without a model.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
Why connect Clay's MCP server through Elaichi
Clay builds and runs this MCP server. Elaichi sits in front of it, so Clay's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Clay's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Clay's tools at the same Elaichi address as every other connected app. Nobody adds Clay's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Clay sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Clay's server. By default, a tool Clay does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Clay
Clay builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Clay team.
For IT and engineering
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.
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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Questions, answered
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, Microsoft Copilot 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 role or a toolbox, and it can never widen it beyond what Clay itself allows.
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 restricting anything that writes or removes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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.
Put Clay in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot