Skip to main content

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 only

    Tool name: add-company-data-points

    Add data points to companies in an existing search.

  • Add contact data points

    Read only

    Tool name: add-contact-data-points

    Add data points to contacts in an existing search.

  • Ask question about accounts

    Read only

    Tool name: ask-question-about-accounts

    Ask a natural language question about one or more accounts available in Clay Audiences.

  • Find and enrich company

    Read only

    Tool name: find-and-enrich-company

    Find and enrich a single company by domain or LinkedIn URL.

  • Find and enrich contacts at company

    Read only

    Tool name: find-and-enrich-contacts-at-company

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

  • Find and enrich list of contacts

    Read only

    Tool name: find-and-enrich-list-of-contacts

    Find and enrich specific named contacts at their companies.

  • Get credits available

    Read only

    Tool name: get-credits-available

    Check if credits are available for the workspace.

  • Get current workspace

    Tool name: get-current-workspace

    Report which Clay workspace this connection is pinned to.

  • Get task

    Read only

    Tool name: get-task

    Get task status and results by task ID.

  • Get task context

    Read only

    Tool name: get-task-context

    Retrieve the current state of a task — all entities, enrichment values, and statuses.

  • Get subroutine input options

    Tool name: get_subroutine_input_options

    Fetch the available dropdown options for a subroutine input that has a configured options source.

  • List subroutines

    Read only

    Tool name: list_subroutines

    List available functions.

  • Load more search results

    Tool name: load-more-search-results

    Fetch the next page (up to 20 more results) of an existing search.

  • Query objects

    Read only

    Tool name: query-objects

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

  • Run subroutine

    Destructive

    Tool name: run_subroutine

    Execute a function on contacts/companies FROM AN EXISTING SEARCH ().

  • Run subroutine direct

    Destructive

    Tool name: run_subroutine_direct

    Execute a custom function on one or more sets of provided inputs.

  • Run subroutine no mapping

    Destructive

    Tool name: run_subroutine_no_mapping

    Run a custom subroutine on search entities.

  • Search companies

    Tool name: search-companies

    Find 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-contacts

    Search 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-name

    Find and enrich specific named contacts at their companies.

  • Track event

    Read only

    Tool name: track-event

    Track 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.

Frequently asked questions