Clay
Clay is a go-to-market (GTM) platform. MCP server to research accounts, find and enrich people with data from 150+ providers, and run ops-built enrichment and outbound workflows (Functions) from your AI client.
Tools
21 available tools
Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.
21 tools found.
Add company data points
Read onlyTool name:
add-company-data-pointsAdd data points to companies in an existing search.
Add contact data points
Read onlyTool name:
add-contact-data-pointsAdd data points to contacts in an existing search.
Ask question about accounts
Read onlyTool name:
ask-question-about-accountsAsk a natural language question about one or more accounts available in Clay Audiences.
Find and enrich company
Read onlyTool name:
find-and-enrich-companyFind and enrich a single company by domain or LinkedIn URL.
Find and enrich contacts at company
Read onlyTool name:
find-and-enrich-contacts-at-companySearch for contacts at a company by role, title, name, or department.
Find and enrich list of contacts
Read onlyTool name:
find-and-enrich-list-of-contactsFind and enrich specific named contacts at their companies.
Get credits available
Read onlyTool name:
get-credits-availableCheck if credits are available for the workspace.
Get current workspace
Tool name:
get-current-workspaceReport which Clay workspace this connection is pinned to.
Get task
Read onlyTool name:
get-taskGet task status and results by task ID.
Get task context
Read onlyTool name:
get-task-contextRetrieve the current state of a task — all entities, enrichment values, and statuses.
Get subroutine input options
Tool name:
get_subroutine_input_optionsFetch the available dropdown options for a subroutine input that has a configured options source.
List subroutines
Read onlyTool name:
list_subroutinesList available functions.
Load more search results
Tool name:
load-more-search-resultsFetch the next page (up to 20 more results) of an existing search.
Query objects
Read onlyTool name:
query-objectsQuery audience accounts, contacts, or deals using natural language.
Run subroutine
DestructiveTool name:
run_subroutineExecute a function on contacts/companies FROM AN EXISTING SEARCH ().
Run subroutine direct
DestructiveTool name:
run_subroutine_directExecute a custom function on one or more sets of provided inputs.
Run subroutine no mapping
DestructiveTool name:
run_subroutine_no_mappingRun a custom subroutine on search entities.
Search companies
Tool name:
search-companiesFind a LIST of companies matching prospecting filters (industry, size, location, funding, tech stack, keywords), expressed as a Search DSL query.
Search contacts
Tool name:
search-contactsSearch for contacts (people) by role, title, seniority, location, or employer, expressed as a Search DSL query.
Search contacts by name
Tool name:
search-contacts-by-nameFind and enrich specific named contacts at their companies.
Track event
Read onlyTool name:
track-eventTrack an analytics event with optional properties.
Compatibility
Connect Clay to the clients your teams already use
27 AI clients can connect to Clay through Runlayer. Pick one for its setup steps and controls.
Why Runlayer
Why connect Clay through Runlayer?
One approved path
Approve Clay once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.
Fine-grained policy
Control who can use each server, tool, and resource, and under which runtime conditions.
Runtime security
Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.
Audit and observability
Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.
