Skip to main content
Book a demo

Connect Clay to Cursor

Give Cursor governed access to Clay’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Clay to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 1

    Approve Clay in Runlayer

    Add Clay from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Clay’s 21 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Clay

    Sign in the way Clay requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Clay from Cursor

    Clay’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

21 Clay tools in Cursor

Runlayer policy decides which of these Cursor users can call. 12 read data only and 3 can change or delete data.

  • Add company data points

    Add data points to companies in an existing search.

  • Add contact data points

    Add data points to contacts in an existing search.

  • Ask question about accounts

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

  • Find and enrich company

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

  • Find and enrich contacts at company

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

  • Find and enrich list of contacts

    Find and enrich specific named contacts at their companies.

  • Get credits available

    Check if credits are available for the workspace.

  • Get current workspace

    Report which Clay workspace this connection is pinned to.

See all 21 Clay tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Clay call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination