Clay
official MCP | Researched | Checked 2026-09-03
The latest Clay guide
30 answers about capabilities, access and practical workflows. Documentation reviewed 2026-10-19.
The catalog details below retain their original check dates. The guide separates documented features from untested connections.
Build reusable enrichment workflows with named inputs and outputs. Clay Functions support company enrichment, ICP scoring and inbound qualification, with centrally managed changes.
- API access
- paid
- MCP support
- official
- Last checked
- 2026-09-03
- Research
- Source researched
Connection and workflow notes
Documentation reviewed 2026-10-18. No authenticated connection test was performed for this update.
Clay’s official MCP connects a user and workspace through OAuth. It is different from community projects that use browser session cookies. Treat their authentication instructions and tool inventories separately.
Official connection
The hosted endpoint is https://api.clay.com/v3/mcp. A compatible client uses OAuth with PKCE; custom platforms can register through Dynamic Client Registration. Workspace policy controls which clients may connect.
Vendor documentationPrepare the workspace
Invite the rep to the workspace and set a default credit limit before they connect. Admins can enable Functions for MCP and set individual limits. A Function needs an output column to return a useful result.
Vendor documentationWhen the wrong workspace connects
Clay documents a common failure: a rep connects before accepting the company invitation and ends up in a personal workspace. Disconnect, accept the invite, then reconnect and choose the company workspace.
Vendor documentationA first test to run
Choose one company domain you already know. Request enrichment, compare the returned identity with the source, and inspect the credit usage. Test a Function separately so you can tell a connection problem from a workflow problem. This is a suggested test, not a result we observed.
Research correction: The older downloadable snapshot contains session-cookie authentication and community tool names. Those details must not be used as instructions for the official server.
Workflows to compare
These are research categories assigned to the product. They do not establish that every task is available through its MCP.
- Enrich a company from a domain: Hand it a domain or company name and get firmographics back.
- Build a target account list: Produce a ranked or filtered account universe from an ICP definition or a set of best customers.
- Find a person's LinkedIn URL from a name and company: Hand it a person's name plus a company name or domain and get the LinkedIn profile URL back. The inverse of enrich-person-from-linkedin-url, which needs the URL as input. Added 2026-09-03 by the owner; see the header.
- Find a work email address: Hand it a person plus a company, domain or profile URL and get a work email back.
- Scrape a web page for facts: Fetch and structure an arbitrary public page. The general-purpose fallback when no structured provider has the record.
- Write CRM records: Create or update records, log activity, or push data back into a system of record.
- Run an automation workflow: Trigger or execute a multi-step workflow across tools, deterministic or agent-driven.
How to use this record
This record is based on source research, not an authenticated test of the product. Product features, API access and MCP actions can differ. Use the linked vendor documentation to confirm the operation you need and the account it will run against.
How to check an MCP before connecting · Research methods · Report a correction
About Clay
Read the company research and follow its original sources. Coverage varies by company.
Skills with examples for this tool
Download the instructions and use them with your agent and the GTMMCPs research MCP.
- Find a GTM tool
Included in the enrichment research example. This is not a tested vendor connection.
- Check an MCP connection
The worked example reviews Clay connection evidence and requirements.
Full capabilities, notes, CLI evidence, and provenance are preserved in the original dataset. Find this record by its ID: 01-clay.