Clay for AI agents
Clay enriches go-to-market data, searching people and companies and running automated workflows to build lists a sales or marketing team can act on. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Clay.
Search for people or companies
Search for people or companies matching a set of criteria before building an outreach list.
Run an enrichment routine
Run a saved routine against a record to pull in missing company or contact details.
Check a routine's results
Check the results of a routine run before pulling that data into a workspace table.
6 Clay actions, graded by risk.
Every Clay action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- clay.get_current_userGet Current User
- clay.get_routine_run_resultsGet Routine Run Results
- clay.get_search_query_referenceGet Search Query Reference
- clay.search_people_or_companiesSearch People or Companies
write
2Create and change things. Allow, or ask the user first.
- clay.run_routineRun Routine
- clay.continue_searchContinue Search
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Clay in three steps.
- 01Your users connect ClayThey add their Clay api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “run Routine” can wait for the user to approve.
- 03Any agent can actYour agent calls Clay through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('clay', { read: 'allow', write: 'ask', // run_routine destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Clay connects.
Users add their Clay api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Clay connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Clay from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Clay and Arc0, answered.
Can I use Clay with Claude, ChatGPT or Cursor?
Yes. Connect Clay to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Clay actions you allow.
How do users connect Clay?
Users add their Clay api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Clay actions can my agent take?
6 in total: 4 read, 2 write and 0 destructive, such as “run Routine”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Clay?
Yes. Allow read actions and deny writes in the Clay policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Clay too?
Yes. The same Clay connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Clay into your agent.
Your users connect Clay once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan