Clay MCP is a feature of 📝Clay that exposes Clay's people and company search, waterfall enrichment across 200+ data providers, and admin-published functions to AI assistants through the 📝Model Context Protocol (MCP), so reps can find contacts, enrich them, and push them to a CRM or sequencer in natural language. It exists because reps increasingly work inside AI assistants rather than spreadsheets, and RevOps teams needed a way to hand them governed workflows without giving up control of write-backs, compliance logic, and enrichment spend. It is built for sales reps working in 📝Claude, 📝ChatGPT, and 📝Codex, and for the Ops admins who govern them, on Launch, Growth, and Enterprise plans.
Key Capabilities
- Natural-language prospecting — Reps search Clay's company and people database in plain language, with cross-entity advanced search and up to 1,000 people results per query.
- Waterfall enrichment — Every email and phone number a rep requests runs through Clay's multi-provider waterfall, so contact data arrives validated rather than from one vendor.
- Governed functions — Admins toggle individual functions "Enable for MCP," turning the team's best playbooks, such as lead scoring or account prep, into tools reps call from chat.
- Spend controls — Admins set a default monthly credit cap per MCP user, per-user overrides, and hard blocks, with usage attributed per user and per function on the dashboard.
- CRM and sequencer push — Reps check new contacts against the CRM for duplicates, then send net-new records to a sequencer or CRM under write rules that Ops defines.
Getting Started
- Confirm the workspace is on a Launch, Growth, or Enterprise plan.
- Add Clay as a connector in Claude, ChatGPT, or Codex and sign in with OAuth.
- Have an admin set per-user credit caps under Settings → MCP users.
- Toggle "Enable for MCP" on each function reps should be able to call.
- Ask the assistant to find, enrich, or push contacts in plain language.