Clay Custom MCP
Clay Custom MCP is a feature of 📝Clay that lets a workspace add an external 📝Model Context Protocol (MCP) server — by name, URL, and key — so that server's tools become callable by 📝Claygent and AI columns. It is the reverse of 📝Clay MCP: instead of exposing Clay to other assistants, it makes Clay an MCP client that reaches into other systems. It is built for GTM engineers who want agents inside Clay to use internal tools or third-party services that have no native Clay integration.
Key Capabilities
- Bring any MCP server — Register an external server by name, URL, and key in workspace settings, and its tools appear to agents running in the workspace's tables.
- Agent tool use — Claygent and AI columns can call the server's tools mid-run, pulling internal data or triggering actions as part of research and enrichment.
- Bring-your-own-key — Calls run against the workspace's own credentials for the external server, keeping access and billing under the customer's control.
Getting Started
- Open workspace settings and go to Accounts, then Custom MCP.
- Add the external server's name, URL, and key.
- Reference the server's tools in a Claygent or AI column and test on a few rows.
