Clay for the single account.
Clay's own MCP server, passed through by the Data Hub for each business unit. With it, the agent enriches companies by domain, finds contacts by role, runs approved Clay functions and queries audiences.
- Vendor MCP · passed through as is
- Coverage: complete
- 8 tools (per vendor) · 8 of them make changes
Read and change.
Your agent works with exactly the permissions of the connected account. Read tools are quick to enable. Tools that change data stay off until you explicitly turn them on.
What your agent can read
- Find and enrich companies by domain or LinkedIn URL.
- Find contacts at a company by role or title.
- Results of running enrichments, and the credit balance.
- On the Enterprise plan: query audiences in plain language and ask questions about accounts, contacts and opportunities.
What your agent can change
- Run Clay functions that are enabled for MCP in your Clay workspace. Those functions can in turn write to the CRM or to sequences, for example.
Only once you enable it, per agent and per tool. If you want, a person also approves each action before it runs.
How teams use Clay MCP.
Marketing, sales and RevOps run these as recurring routines or on request.
- 01
Account briefing before the call
30 minutes before the meeting- Enrich the company by domain
- Find three decision-makers by role
- Write a briefing with conversation starters
ResultYou go into the call with a briefing and don't have to look anything up yourself.
- 02
Complete the buying committee
A deal is stuck- Search the company for missing roles such as finance or IT
- Enrich the contacts
- Put them together as a suggestion for the deal
ResultYou know everyone who has a say in the decision.
- 03
Ask your audience
During campaign planning (Enterprise)- Ask the audience a question in plain language
- Summarize the matching accounts
ResultAnswers from your own Clay data.
Built-in safeguards
- Clay doesn't mark any tool as read-only, so the Data Hub treats all of them as tools that make changes. None of them are enabled automatically.
- Separate connection through Clay sign-in. Clay workspace admins can block unverified MCP clients.
- If you want, changes only run after a person approves them, for example the team lead: in the Data Hub, in Slack or via a link. On top of that, each agent has daily and hourly limits.
- Guardrails for every agent: deletes and changes to more than 10 records need approval by default, an emergency brake kicks in on a run of deletes, and you can set your own rules per tool.
- Each connection has an access level: Read, Write or Admin. Where the vendor allows it, the Data Hub only requests the permissions for that level.
- Credentials are stored encrypted in the Data Hub, and the agent never sees them. Every call is logged.
What it can't do
- Built for individual lookups (around 1–20 contacts): at most 100 results per search, no CSV uploads, no writing to audiences, no tables. For larger volumes, use the Clay integration with batch runs.
- Enrichments cost Clay credits.
Clay decides which tools exist through its own MCP server. The hub passes on everything that server offers and refreshes the list every 24 hours.
Connect Clay MCP to your agents.
In 30 minutes, we'll show you the Data Hub with your own tools.