Clay

Clay

Curated major addition platform in gtm data enrichment and workflow building with material relevance to the Marcom operating stack and a first-party developer surface.

CRM, revenue & customerSystem of recordAgent-accessible SaaS
System roleSystem of record
Access maturityAgent-accessible SaaS
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Expose approved Clay functions, research agents, enrichments and workflow capabilities to compatible clients; admins govern functions, permissions and credit budgets

02 · Data you can retrieve

Expose approved Clay functions, research agents, enrichments and workflow capabilities to compatible clients; admins govern functions, permissions and credit budgets

03 · Actions and write paths

The targeted review confirmed this Clay capability surface: Expose approved Clay functions, research agents, enrichments and workflow capabilities to compatible clients; admins govern functions, permissions and credit budgets. It did not normalize every mutation tool. Treat writes as unapproved until each current tool, scope, plan and approval behavior is verified.

04 · Authentication and permissions

For Clay, the audited authentication model is: Authentication model is documented by the vendor; inspect the cited source before implementation. The effective permission model is: Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary. Reconfirm the cited first-party source before implementation.

05 · Monitoring, approval, and recovery

Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions. Current first-party Clay MCP documentation supersedes the older GitHub proof-of-concept; optimized for targeted operations rather than bulk table-scale execution.

06 · Gaps and implementation limits

Current first-party Clay MCP documentation supersedes the older GitHub proof-of-concept; optimized for targeted operations rather than bulk table-scale execution.

Agent access

MCP and adjacent posture

Verified first-party provider MCPVendor-hosted remote MCPCurrent documented service

Role: provider

Read scope: Expose approved Clay functions, research agents, enrichments and workflow capabilities to compatible clients; admins govern functions, permissions and credit budgets

Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Clay ships these experiences.

Single-platform patterns

  • Signal enrichment and account-research workbench
  • Account journey room
  • Pipeline-quality debugger
  • Customer expansion cockpit
Use in the brief composer →

Multi-platform compositions

  • Clay + marketing or intent platform: account journey room
  • Clay + conversation or support system + analytics or warehouse: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
MCP / agent-role validationRepresentative source
https://university.clay.com/docs/mcp-settings ↗

Current first-party Clay MCP documentation supersedes the older GitHub proof-of-concept; optimized for targeted operations rather than bulk table-scale execution.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

MCPSource inventory
https://github.com/clay-inc/clay-mcp ↗

First-party MCP documentation or product announcement recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

APISource inventory
https://docs.clay.com/en/api-reference/introduction ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer docsSource inventory
https://docs.clay.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.clay.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.