Clay
Give the Sazabi agent tools to search contacts, interactions, and workspace workflows, and create or update records and workflows, for enriched prospecting and relationship data.
About
Clay is an MCP connector that gives the Sazabi agent tools to work with your Clay CRM data. Clay's MCP server authenticates via OAuth with dynamic client registration. Once connected, the agent can search your Clay workspace for contacts, browse interaction history, retrieve workflow data, and create or update records and workflows. Write tools are governed by the per-connection read-only toggle.
What the agent can do:
- Search contacts, companies, and enrichment data
- Browse interaction and note history
- Access workspace table data and views
- Retrieve workflow and automation results
- Create and update records and workspace workflows
Prerequisites
- An active Clay workspace
- Permission to authorize third-party OAuth applications in Clay
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Clay in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to Clay to authorize, then back.
Set up with the CLI
You can also connect Clay with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
Clay authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect clayAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized.
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.