Included as an operations-curated enrichment surface where workspace admins expose selected Clay Functions to sales reps, apply monthly credit budgets, and optionally grant read-only access to owned CRM accounts through Audiences, while built-in tools handle targeted people and company research.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
People and companies, enrichment results, account research, reusable Functions and their inputs/outputs, MCP users and monthly credit budgets, optional Audiences account and opportunity data, and downstream systems invoked inside enabled Functions.
Search for people or companies, research accounts, enrich selected contacts, list and invoke admin-enabled Functions, and—on eligible Enterprise beta workspaces—query synced Audiences fields for owned or explicitly broadened Salesforce accounts. MCP cannot browse raw tables or arbitrary workspace data.
Clay MCP does not provide blanket table CRUD. An enabled Function can run any enrichment or downstream action configured inside it, including a Sequencer step or connected email action; clicking Open in Clay can create a table. Function side effects therefore depend on the admin-published workflow.
Users connect through Clay’s OAuth flow in supported official connectors. Viewer users cannot complete MCP OAuth; Sales Rep is the preferred MCP-only role, while Editor and Admin can also connect. Workspace admins choose enabled Functions, credit caps, and optional Audiences account scope.
Admins set a default monthly MCP credit limit and per-user overrides, monitor live usage and connected platforms, enable Functions individually, and can restrict reps to Salesforce-owned accounts. Setting a user’s cap to zero hard-blocks actions; removing the user from the workspace removes access.
MCP is designed for targeted or moderate-scale work: results paginate in groups of 20 up to 100, with no dedicated bulk upload. True table-scale processing remains in Clay. Self-hosting and arbitrary custom-agent connections are not supported. Audiences controls are Enterprise Open Beta, and admins cannot directly revoke a connection from MCP users.
Agent access
Support: Official MCP server
Read scope: Allow targeted people/company search, account research, selected enrichment, enabled Function results, and read-only Audiences questions within synced fields and configured account ownership. Do not represent MCP as table browsing or full-workspace access.
Write scope: No uniform write catalog exists beyond the workflow an admin exposes. Treat every enabled Function as its own capability contract: it may only enrich and return data, or it may call Sequencer, email, CRM, or another connected destination according to its columns.
Authentication: Clay-managed OAuth through an official supported connector; CLI-initiated Claude connections are rejected. The user must join the intended workspace before connecting and hold Sales Rep, Editor, or Admin rather than Viewer.
Approval boundary: Before invoking a Function, show its exact name, inputs, contained enrichments, estimated credits when visible, and every downstream destination or send step. Require confirmation for Sequencer enrollment, email, CRM writeback, or high-credit enrichment; a friendly Function name is not sufficient evidence that it is read-only.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Clay ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Current first-party Clay MCP documentation supersedes the older GitHub proof-of-concept; optimized for targeted operations rather than bulk table-scale execution.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
