Files
roshansada 08631ab2ef Shorten plugin descriptions
Replace "Connect to [tool]" openers, em-dash asides, and MCP server
boilerplate with brief verb-first copy in plugin and marketplace
manifests. Resync the README table that mirrors them, adding rows that
had drifted out (teaching, ralph-loop, playwright, github, zoom, clay).
Also refresh the stale read-only X marketplace copy and clean em-dashes
from the Salesforce server URL help text.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-17 18:34:06 -07:00
..
2026-08-07 16:19:34 -07:00

Clay

Cursor plugin that connects agents to Clay through Clay's official hosted Model Context Protocol server.

Find and enrich people and companies across 150+ data providers, run AI research agents (Claygent), and trigger your team's approved Clay workflows from the signed-in Clay workspace.

Install

  1. Open Cursor Settings → Plugins.
  2. Search for Clay.
  3. Click Install, then complete the Clay sign-in prompt.

Or run /add-plugin clay in chat.

MCP

{
  "mcpServers": {
    "clay": {
      "type": "http",
      "url": "https://api.clay.com/v3/mcp"
    }
  }
}

Auth is OAuth 2.1 against Clay with Dynamic Client Registration (DCR) and PKCE. Cursor registers itself and prompts for Clay sign-in when the plugin connects — there is no API key or client ID to configure.

Before you connect

You need a Clay account with access to a workspace.

Your Clay workspace admin may need to allow MCP client connections under Clay workspace Settings → MCP. If sign-in succeeds but tools fail, check with your admin.

What agents can do

Category Capabilities
People & companies Search Clay's data universe with natural-language criteria
Enrichment Pull emails, phone numbers, firmographics, technographics, and other data points across 150+ providers
Research Ask Claygent open-ended questions about accounts and contacts
Workflows Trigger Clay tables and workflows your team has approved for MCP access

Notes

  • Tool calls run as the Clay user who authorizes the connection and cannot exceed that user's permissions.
  • Workflow triggers are limited to workflows approved for MCP access in the Clay workspace.
  • Connections appear in your Clay workspace's MCP client list, labeled with the Cursor client name.
  • Revoke access at any time from Clay workspace Settings → MCP.

Docs

License

MIT