Clay MCP connector for AI agents

Clay MCP tools for AI agents

CALL ANY TOOL

12 tools covering ask, add.

claymcp_add_company_data_points

Add data points to companies in an existing search. supports

Add data points to companies in an existing search. supports enriching all companies or specific companies via entityids. use for tech stack, funding, headcount, competitors, or any custom research question about companies.

Parameters

Name

Type

Required

Description

dataPoints

array

Required

The data points to apply to the company

rationale

string

Required

Always provide a brief explanation of why you are calling this tool

taskId

string

Required

The task ID identifying the search to add company data points to

entityIds

array

Optional

Optional. Array of entityIds to enrich. When omitted, enriches all companies.

claymcp_add_contact_data_points

Add data points to contacts in an existing search. supports

claymcp_ask_question_about_accounts

Ask a natural language question about one or more accounts a

claymcp_find_and_enrich_company

Find and enrich a single company by domain or linkedin url.

claymcp_find_and_enrich_contacts_at_company

Search for contacts at a company by role, title, name, or de

claymcp_find_and_enrich_list_of_contacts

Find and enrich specific named contacts at their companies.

claymcp_get_credits_available

Check if credits are available for the workspace. returns ha

claymcp_get_subroutine_input_options

Fetch the available dropdown options for a subroutine input

claymcp_get_task

Get task status and results by task id. handles all task typ

claymcp_get_task_context

Retrieve the current state of a task — all entities, enrichm

claymcp_list_subroutines

List available custom functions in the workspace. call this

claymcp_query_objects

Query audience accounts, contacts, or deals using natural la

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="claymcp")

mcp = MultiServerMCPClient({
    "claymcp": {
        "url": "https://mcp.scalekit.com/claymcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "claymcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/claymcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "claymcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/claymcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="claymcp")
# Connect to MCP at https://mcp.scalekit.com/claymcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Track an analytics event with optional properties?

Copy the prompt

Copied

Run a custom subroutine on search entities?

Advanced

Copy the prompt

Copied

Query audience accounts, contacts, or deals using natural language?

Copy the prompt

Copied

List available custom functions in the workspace?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Clay MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Clay MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Clay MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Clay MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

SALES

Outbound prospecting agent

Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.

Apollo

View agent

GTM

HubSpot to Slack updates agent

Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.

HubSpot

Slack

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Clay as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Clay OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Clay?
Yes. Pass a tool name filter to listScopedTools so the marketing agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Clay.

What happens when a user revokes Clay access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Whose Clay credits do enrichment runs consume?
The authorizing user's workspace credits, attributed to that user. Company and contact enrichment, list runs, and account questions all log who triggered the spend across Clay's 150+ data providers.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit