Clay
by Clay
Search Clay's GTM database and enrich contacts and companies from an AI agent. Seven tools listed, one of which reads the credit balance — but enrichment spends money per record, and admin-enabled Functions add tools this listing does not name.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Clay via MCP
https://api.clay.com/v3/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Clay Tools & Capabilities (7)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Enrichment spends money and no tool prices it.
get-credits-availablereads the balance; nothing reads the rate. Clay places the cost preview in its web app, which an MCP client cannot see. Leave the fourdataPoints-bearing tools on per-call confirmation. - Retries bill again. Clay lists stopped-midway runs and duplicate enrichments among the causes of unexpected deductions, and publishes no idempotency key for MCP. A timed-out enrichment must not be retried blindly.
- Top-ups carry a 30% premium, so an exhausted balance is more expensive to refill mid-cycle than to have planned for.
- The tool list is a floor. Clay's troubleshooting documentation names
List subroutinesandrun_subroutine_no_mapping, neither of which appears in Anthropic's directory entry or Clay's own connector tool documentation. The second one executes arbitrary workspace Functions. - One OAuth scope,
mcp, and no boundary inside it. Nothing at consent separates a free search from a paid enrichment, or a read from a Function that sends mail. The real boundary is the per-user credit limit, which is a Clay setting rather than an OAuth grant. - A Viewer can still spend. Clay states the Viewer restriction governs the web app, not MCP. Role-lowering is not an MCP control; removal or a zero credit limit is.
- An OAuth connection cannot be revoked from the admin UI. Clay states admins "cannot directly revoke a rep's MCP connection"; the documented remedies are removal from the workspace or a zero limit.
- Results cap at 100. Clay documents pagination in groups of 20 up to five pages, and directs anything larger back to the Clay web app.
- Clay cannot tell a company AI account from a personal one. Asked whether a team can require company-managed AI accounts, Clay answers "Not from Clay" — client allow-listing controls the platform, not the account on it.
Customdata points have no published price. The documented shape sends free-text research instructions to a web-browsing agent; Clay publishes rates for named data points but not for this.- Credit spend limits on workbooks are Enterprise-only, and Clay notes limits do not automatically reset when a billing cycle does.
- Self-hosting is not supported. Clay states every client connects to its hosted server.
Frequently asked questions
Yes, on enrichment. Clay documents that search itself is free but credits are consumed the moment MCP triggers a real enrichment such as an email, phone number or tech stack. Clay puts a fully enriched record at 6 to 20 Data Credits, and its own Launch pricing sells 2,500 credits for 125 dollars, which is 5 cents a credit.
It can read the balance, not the price. The get-credits-available tool returns how many credits the workspace has left, which is more accounting surface than most metered connectors expose. But no tool returns the per-data-point rate, and Clay says that cost preview lives in the enrichment panel inside the Clay web app, which an MCP client never sees.
Seven plus however many Functions your admin enabled. Anthropic lists seven and Clay's own tool documentation names the same seven, so the fixed part agrees exactly. But Clay's troubleshooting guide names two further tools that neither list carries, and one of them executes any custom Function your workspace has published to MCP.
Not with the seven listed tools, and yes through a Function. Clay's MCP FAQ states plainly that without a Function configured for it, an AI assistant can still send through a connected email provider like Gmail, and that a Function built around a sequencer column lets a rep pick which sequence to enrol someone in from the widget.
A single scope named mcp. Clay's RFC 9728 descriptor and its authorization server metadata both advertise scopes_supported as exactly that one value, and Clay's own developer documentation confirms mcp is the only scope available to publicly registered clients. Nothing at the OAuth grant separates reading a company record from spending credits enriching one.
Yes, and Clay says so directly. Clay's MCP security documentation states that the Viewer restriction governs the Clay web app, not MCP, and that a Viewer can still trigger runs. Clay's advice is that lowering someone's role will not stop them; remove them from the workspace, or set their credit limit to zero, which hard-blocks further actions.
Work emails, phone numbers and profile detail about named third parties. Clay's tool documentation lists Email and Summarize Work History as contact data points, and the connector filters people by schools attended, certifications, profile languages and months in role. These people never consented to your agent, so treat the output as regulated personal data.
A per-user credit limit an admin sets before anyone connects. Clay documents a workspace default limit in Settings then MCP users, plus per-user overrides, with live usage tracked against each. Clay's guidance is to set the default before reps connect, because reps who connect first inherit no cap unless a default already exists.
Sources
- Clay connector tool documentation, "Clay <> Claude MCP Server Documentation" (retrieved 2026-08-22, 307 to
app.notion.com/p/clayrun/...). This is thedocumentationURL Anthropic's directory publishes for this connector; the page is client-rendered, and its content was read through Notion's own public page API. · retrieved 2026-08-22 - Clay University, "MCP in Clay" (admin settings, Functions, credit limits) (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay University, "MCP troubleshooting and FAQs" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay University, "MCP Security & Privacy" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay University, "Actions & Data Credits" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay University, "Credit spend limits FAQ" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay University, "Do Not Contact (DNC) compliance & best practices" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay University, "Outreach in ChatGPT" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay pricing, plan tiers and credit list prices (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay developer documentation, "Connect your platform to Clay MCP" (retrieved 2026-08-22) · retrieved 2026-08-22
- Clay developer documentation index,
llms.txt(retrieved 2026-08-22).developers.clay.com/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis expressly permitted. · retrieved 2026-08-22 - Live OAuth posture check: anonymous POST to
https://api.clay.com/v3/mcpreturned 401 withWWW-Authenticate: Bearer resource_metadata=...; RFC 9728 descriptor athttps://api.clay.com/.well-known/oauth-protected-resource/v3/mcpand authorization server metadata athttps://api.clay.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Clay support — <mailto:support@clay.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Clay
- Tools
- 7
- Domain
- api.clay.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.