LABSCO SUMMARY
No MCP surcharge and an admin credit cap is the combination that makes this safe to hand out.
Enrichment platforms usually price API access above UI access, which quietly punishes automation. Clay charging the same rate removes the reason to avoid the connection. The cap matters more: an agent enriching a list can spend a lot quickly, and a per-rep ceiling is the difference between a surprise and a budget. One consent detail to expect — clients registered through open DCR show as 'Unverified application', which is normal here and not a warning to click past without reading.
What it is
Clay's endpoint over their GTM data platform. Tools run scoped to one workspace, chosen at the consent screen rather than inherited from the account.
What you get
Clay's enrichment and table work through the platform's API.
Requirements
OAuth 2.1 with PKCE and open dynamic client registration, scope mcp. MCP calls consume the workspace's Clay credits at the in-product rate, admins can cap credits per rep, and 500 free credits are granted to start.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Enriching a list from the conversation
Run Clay's enrichment against the chosen workspace without switching tools.
02
Keeping spend bounded
Cap credits per rep so an agent's exploration cannot drain the workspace.
03
Scoping access to one workspace
The workspace is chosen at consent, so the connection does not reach the whole account.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 authorization-code + PKCE S256 (scope 'mcp'); open Dynamic Client Registration at https://api.clay.com/oauth/register; authorize at https://app.clay.com/oauth/authorize; token at https://api.clay.com/oauth/token; device flow advertised but not registrable via DCR
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api.clay.com/v3/mcpRequirements
- OAuth 2.1 authorization-code + PKCE S256 (scope 'mcp'); open Dynamic Client Registration at https://api.clay.com/oauth/register; authorize at https://app.clay.com/oauth/authorize; token at https://api.clay.com/oauth/token; device flow advertised but not registrable via DCR
