Skip to content
ANY//
Anysite Blog· 5 min read

Use Anysite MCP in Clay for Flat-Rate Social Data Enrichment

IntegrationsMCPGuides

Clay bills enrichment by the record, which is fine until the volume climbs. Anysite MCP takes the other approach: MCP plans are flat monthly plans with no per-request meter, so the connection costs the same whether a table has a hundred rows or ten thousand.

Here is what the Anysite MCP server actually does, how to connect it to Clay, and where the API line fits instead.

What the MCP Server Gives You

The Anysite MCP server exposes five meta-tools rather than one tool per endpoint:

  • discover — find the right endpoint for the job across the catalog
  • execute — call that endpoint and get typed JSON back
  • get_page — read any public URL directly
  • query_cache — re-query results you already pulled, without a fresh call
  • export_data — hand a result set off as a file

An earlier version of the server published a separate tool per platform endpoint. Every client then had to load a long tool list before asking a single question, and the list grew every time the catalog did. The meta-tool design replaced it: the agent asks in plain language, discover resolves the request to an endpoint, execute runs it. New sources appear behind the same five tools.

What you can pull

Profiles, company records, employee lists, posts, comments, followers, job listings and search results across Instagram, Twitter/X, Reddit, YouTube and business data — plus any public web page by URL. The JSON shape is consistent across platforms, so the second Clay column is a copy of the first rather than a rebuild.

Two Ways to Connect Anysite to Clay

Clay gives you two places to put Anysite, and they bill differently.

The MCP path plugs the Anysite MCP server into Clay’s AI agent. You paste one URL, authorize once, and the agent picks the endpoint for each row. This is the path an MCP plan covers.

The HTTP column path puts one specific Anysite endpoint URL into Clay’s HTTP API column with your key in the header. That path runs on an Anysite API key and bills per credit — one credit per successful enrichment row, and a row that returns nothing doesn’t bill.

Both paths can sit in the same table.

Which Plan Covers Which Path

MCP plans are flat: $30, $99 or $199 a month. They cover the MCP server — the five meta-tools, every source in the catalog — from Claude, Cursor, ChatGPT or Clay’s AI agent. They do not include the REST API or the command line.

The API line is usage-based and starts at $49/month. One API key reaches REST, the CLI and the MCP server, all billed per credit. Access runs one way only: an API key also works over MCP, but an MCP plan does not unlock REST or the CLI.

So if you are enriching from Clay’s agent, an MCP plan is enough. If you also want HTTP columns, or the same data inside your own pipelines, that is the API line.

Setup

  1. Open your Anysite account. Start the 7-day free trial at app.anysite.io — it includes 1,000 credits with full endpoint access.
  2. Add the MCP server in Clay. In Clay’s AI agent settings, paste the MCP URL https://mcp.anysite.io/mcp and authorize with one-click OAuth. Two fields, and the connection is live.
  3. Run a column. Add an enrichment column, describe what you want in plain language, and run it on a few selected rows before the whole table.

Full walkthrough in the docs →

What This Looks Like in a Table

Three patterns come up most often.

Prospecting. A table of target companies with one column asking for people at each company whose title matches the roles you sell to. The agent resolves company to people itself — you don’t map endpoints.

Account monitoring. A watchlist of accounts with columns for recent posts and recent hires, re-run on a schedule. Because the plan is flat, re-running that table every week costs what running it once costs.

Creator research. A list of handles with columns for profile stats and recent post performance on Instagram or YouTube — the kind of data most contact databases don’t carry at all.

Throughput and Fair Use

Flat is not the same as uncapped. There is no per-request meter and no credit counting on an MCP plan, but throughput is fair-use: the server paces heavy bursts to keep accounts stable, and sources have their own pace that no provider can wish away.

Everyday enrichment runs comfortably inside that. If your agent works all day and you feel the ceiling regularly, nothing breaks — the agent is told in the conversation and picks up again shortly after. Regular ceilings are the signal to move to MCP x5 or MCP x15, and upgrades apply instantly.

What Anysite MCP Does Not Do

Anysite reads public web data. It is not a contact database, so it does not provide:

  • email discovery or email verification
  • phone number lookup
  • proprietary firmographics such as revenue or headcount estimates

If your workflow needs those, keep the provider you already use for them and let Anysite cover the platform data. Both live in the same Clay table.

Questions

Does an MCP plan work outside Clay? Yes. The same connection works from Claude, Cursor, ChatGPT and other MCP-compatible clients. It covers the MCP server only — REST and the CLI belong to the API line.

How do the two paths bill together? The MCP path is covered by the flat MCP plan. The HTTP column runs on an API key at one credit per successful row. Mixing them in one table is fine; they simply draw from different meters.

Can I cancel anytime? Yes. MCP plans are month-to-month and cancel from your dashboard.

Is there a free trial? Yes — 7 days with 1,000 credits and full endpoint access.

What happens when a platform changes its layout? Anysite maintains the parser behind the endpoint, so the JSON your Clay columns are mapped to stays the same. Nothing to rewire on your side.

Enrich your next Clay table on live data. Start for free →