Hosting

hosted

Transport

Streamable HTTP

Endpoint

https://api.clay.com/v3/mcp

Authentication

OAuth 2.1 with dynamic client registration and PKCE; workspace client policy and selected membership apply.

Requirements

• Clay user account and membership in the selected workspace
• MCP client/platform that supports dynamic client registration, OAuth authorization code with PKCE, token refresh, and MCP session headers
• Workspace admin must allow the client and enable the desired Functions/MCP access
• Credit use follows the workspace's Clay credits and admin limits; relevant features are plan-gated

Setup steps

1. This official guide is primarily for AI platform developers: register the client once at https://api.clay.com/oauth/register with redirect_uris, grant_types authorization_code/refresh_token, token_endpoint_auth_method, and scope mcp. PKCE is mandatory.
2. At user connection time, direct the user to the Clay authorization endpoint https://app.clay.com/oauth/authorize with registered client_id, callback redirect_uri, scope=mcp, and S256 PKCE parameters; the user signs in, consents, and chooses a workspace.
3. Exchange the five-minute authorization code at https://api.clay.com/oauth/token, securely store/rotate the returned credentials, and call https://api.clay.com/v3/mcp using Bearer token. The first MCP call must initialize; preserve Mcp-Session-Id for later calls.
4. Ask a workspace admin to enable the client under MCP users / Allowed MCP clients, invite/assign appropriate Sales Rep access if applicable, set credit limits, and enable approved Functions.
5. For end users of already registered clients, choose the Clay connector in that client and complete browser consent; do not ask the end user to create an OAuth client unless building/registering a platform.

Partial list: Clay’s official MCP troubleshooting page names run_subroutine_no_mapping; available Functions and enabled actions vary by workspace.

• run_subroutine_no_mapping

  Execute custom Clay Functions without automatic field mapping.

  01

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Available tools and Functions depend on workspace settings, user membership, enabled client policy and permissions.
• Calls consume connected workspace credits; admins can set per-user limits.

• Public docs explain the MCP protocol and client registration but do not publish a static tool inventory; tools depend on workspace Functions and permissions.

• official workspace configuration reference

  Explains admins choose which reps, credits, and custom Functions are exposed over MCP; custom Function names are user-defined.

• official surface distinction

  Clay states its Agent Plugin does not include MCP and that MCP for Reps is a separate connection/workflow.

• official documentation

  Current publisher or maintainer documentation reviewed 2026-10-28T19:00:00.000Z.

• official crawl4ai tool inventory audit

  Crawl4AI 0.9.5 fetched the selected documentation page. No exact MCP tool identifiers were present in the captured page content; where attempted, the hosted tools/list endpoint required authorization.

• official mcp tool reference

  Clay’s MCP troubleshooting documentation explicitly names the action run_subroutine_no_mapping and states it executes custom Functions; the list is partial and workspace actions can be individually enabled/disabled.

Documentation checked 2026-10-29T22:49:39.304Z. Connection has not been runtime tested.