Reads
Answer straight away. Nothing changes.
- Operation discovery and request schemas
- Bounded provider reads and supported analytics
Commerce & CRM · MCP server
Your sales stack, through MegaMCP
MegaMCP is a hosted Clay MCP server that lets Claude, ChatGPT and Cursor read authorized Enterprise table fields, credit balance, routine results and supported workflow queries and propose supported searches and enrichment routine requests after review that you approve.
LiveConnect it from your dashboard today.
Live demo
Ask in plain English. Your AI reads Clay with real MegaMCP tools, then hands you a plan. Nothing moves until a person clicks Approve, and supported changes can be undone.
Tools in this example
clay_readReads live dataclay_proposeProposes a change planRead the authorized table and prepare an enrichment routine.
clay_readDoneauthorized Enterprise tableclay_proposeWaiting for approvalplan readyPending cells remain pending. The routine request is prepared with the exact selected inputs and awaits review.
Read the routine's results separately to verify completion.
What your AI can do
Discover supported official API operations, read live data and prepare exact actions for human approval. Reporting uses the same encrypted, client-bound connection. This list comes straight from the running product: 2 read tools and 1 write tool.
Answer straight away. Nothing changes.
Each one returns a plan with a diff. Nothing moves until a person approves.
Fixed vendor-workspace client scope. Exact proposals, provider quota and no replay of uncertain writes. Credential administration, billing, permanent deletion and binary transfers remain in the vendor dashboard.
Plus complete diff previews, human approvals and the flight recorder on every connection. Live changes require a paid plan.
| What it does | Tool id | Type |
|---|---|---|
| Clay operations | clay_list_operations | Read |
| Read Clay | clay_read | Read |
| Propose Clay action | clay_propose | Change |
Example prompts
Paste any of these into Claude, ChatGPT or Cursor once Clay is connected.
“Show the clay operations available to this client.”
“Review clay performance and propose the next action.”
“Query the authorized table for the selected company domains and return only these fields.”
“Show pending and errored enrichment cells separately from successful cells.”
“Read the current credit balance without counting it as period spend.”
“Show the exact schema for this enrichment routine.”
“Prepare one routine run using these approved inputs and wait for review.”
“Retrieve the results of this existing routine run.”
Setup
About two minutes for Claude, ChatGPT or Cursor. Nothing to install.
Start a free workspace and open Connections. Customer API key and authorized table IDs. Structured tables require Enterprise access.
Every app uses the same server URL.
https://megamcp.com/api/mcpTry “Show the clay operations available to this client.” Reports answer straight away. Anything that changes Clay comes back as a plan for you to approve.
Safety
The same loop guards every MegaMCP connection: ask, see the diff, approve, undo.
Clay write tools never touch Clay directly. They return a plan, and a person approves it in the dashboard, or in chat if an admin allows it.
Every plan lists each change with its before and after values, so you see exactly what will move before it does.
Supported changes reverse through a separately reviewed undo plan. Anything that can't be undone is marked before you approve it.
Platform checks stop stale edits, and the flight recorder logs every tool call, plan and approval, with who did it and from which AI app.
| Time | Event |
|---|---|
| 09:14 | clay_list_operations |
| 09:15 | Plan created by Claude |
| 09:16 | Approved by Ana |
FAQ
Yes. As of October 2026, Clay publishes an official MCP server for find-and-enrich tools and Functions. MegaMCP's native connection uses Clay's public REST API, with authorized Enterprise table reads and reviewed routines. It does not relay every tool from Clay's hosted MCP server or invent unsupported table-edit operations.
An MCP (Model Context Protocol) server lets AI assistants such as Claude, ChatGPT and Cursor use Clay through tools. MegaMCP's hosted Clay MCP server gives your assistant 2 read tools and 1 write tool for authorized Enterprise table fields, credit balance, routine results and supported workflow queries, and every change waits for a human approval.
Yes. MegaMCP is a remote MCP server with OAuth sign-in, so one URL works in ChatGPT (as an app, with developer mode on), Claude (as a custom connector), Cursor, Claude Code and VS Code. Your AI app's own plan decides whether it can add custom MCP servers.
Yes, with your approval. It can propose supported searches and enrichment routine requests after review changes. Each one comes back as a plan with a line-by-line diff and waits for a human before anything moves. Fixed vendor-workspace client scope. Exact proposals, provider quota and no replay of uncertain writes. Credential administration, billing, permanent deletion and binary transfers remain in the vendor dashboard.
Customer API key and authorized table IDs. Structured tables require Enterprise access.
Reading Clay is free on MegaMCP's Free plan (100 reads a day, no card). Approved changes are included in every paid plan, from $19/month after a 5-day free trial, with unlimited runs and no credits. MegaMCP adds no markup: any subscription or API usage with the vendor stays between you and them.
Your Clay credentials are encrypted at rest (AES-256-GCM) and bound to their connection, and MegaMCP never trains AI models on your data. Your AI only sees the accounts you switch on, members limited to certain clients only see those clients, and every tool call lands in the flight recorder.
5 days. On the house.
No credit card to start. Every workspace comes with a sandbox ad account, so you can watch the whole ask, diff, approve, undo loop before you connect anything real.
New integrations, platform approvals, the occasional dark joke. One or two emails a month. Unsubscribe anytime.