Prospecting · MCP server

Crustdata MCP and the Yalc Framework

The single most important MCP for any Yalc operator. 14 prospecting and intelligence endpoints surfaced as native Claude tools, with one round of authentication and zero glue code.

Try Crustdata →

Yalc Fit Score

10/10

Tools exposed

14 endpoints

Distribution

Via Composio

Auth

API key + OAuth

Last reviewed

2026-04-29

Install

Add Crustdata to Claude Code in one command

claude mcp add --transport http crustdata-composio "YOUR_COMPOSIO_MCP_URL" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

Get COMPOSIO_API_KEY from composio.dev. Generate the MCP URL in Python with the Composio SDK (composio.create(user_id, toolkits=["crustdata"])). Replace both placeholders, run the command, restart Claude Code, then complete OAuth on first call.

What it does

Crustdata, plainly

Crustdata distributes its MCP server through Composio rather than as a standalone npm package. The advantage is one Composio API key gives you not just Crustdata but every other Composio toolkit you opt into. The endpoints exposed cover the meaningful Crustdata API surface: people enrichment, company search and screener, LinkedIn posts retrieval, web traffic, headcount timeseries, job listings, and funding milestone data.

For Yalc workflows, this is the highest leverage MCP we install. Most Yalc prompts that begin with "find me…" or "enrich these…" route through Crustdata. Native Claude tool calls mean Claude composes Crustdata queries inside the conversation without HTTP plumbing per call.

Where it slots in

Position in the GTM operating system

Intake

→

Enrich

→

Score

→

Route

→

Draft

→

Send

→

Listen

The Crustdata MCP sits at the **intake** node of every Yalc workflow that touches people or company data. Claude calls Crustdata directly during the conversation, returning structured JSON that flows downstream into enrichment, scoring, or send.

Because the tool surface is exposed as native Claude tools (not custom code), Yalc skills compose Crustdata queries with the same idiom as any other tool call. That's the whole reason MCP exists, and Crustdata is one of the cleanest examples in the GTM space.

The Yalc Framework

Deploying the Crustdata MCP inside Yalc workflows

Workflow position

The data intake node. Crustdata runs the search or enrichment, results flow downstream. Yalc workflows almost always pair Crustdata with FullEnrich (for missing emails) or Predictleads (for live signals).

Prompt patterns

Copy paste prompts for Claude Code that invoke the Crustdata MCP.

Yalc, find every Series A to B SaaS company in DACH with 50 to 200 employees that posted a job listing for "Head of Growth" in the last 30 days. Output 100 results to Notion. → Yalc composes Crustdata company_search + job_search queries inline, joins, writes to Notion.

Yalc, for these 200 LinkedIn URLs, enrich current employer, seniority, and the last 5 LinkedIn posts via Crustdata. Tag in the Unified Leads DB. → Yalc batches Crustdata person enrichment + LinkedIn posts retrieval.

Yalc, pull web traffic data for our top 10 target accounts over the last 6 months. Flag any with month over month spikes above 30 percent. → Yalc invokes Crustdata web traffic timeseries, applies threshold logic, surfaces winners.

Chaining recommendations

UpstreamYalc prompt or ICP definition (no upstream)

DownstreamCrustdata → FullEnrich (if email missing) → Instantly or Unipile or HeyReach

Anti patterns to avoid

Don't run people search without first validating filter values via the autocomplete endpoints. The Composio MCP exposes both. You'll burn credits otherwise.

Don't enrich a person before scoring the company. Company filters are cheap, enrichment costs more credits. Filter first, enrich second.

Don't try to use the Crustdata MCP outside Claude Code or another MCP capable client. The Composio install assumes a Claude or Cursor or Codex host.

Compatibility

Tested in Claude Code (primary). Composio publishes installs for Cursor and Codex via the same Composio MCP URL, swapping the host's `mcp add` command syntax. Claude Desktop also works with the standalone Composio MCP URL.

Operator take

Pros, cons, who it's for

Pros

14 endpoints exposed natively. The full Crustdata API surface in one MCP.
Composio handles auth and key rotation. One credential covers Crustdata plus other toolkits.
Native Claude tool calls. No custom HTTP code in your Yalc skills.
Real time signal data (LinkedIn posts, headcount, job listings) surfaced on demand.
Active maintenance. Composio ships toolkit updates regularly.

Cons

Distribution is via Composio, not the official Anthropic MCP registry. One extra vendor in the chain.
Requires both a Crustdata API key and a Composio API key. Two credentials to manage.
First call triggers an interactive auth flow. Fine for desktop use, friction for headless agents.
Composio's OAuth proxy adds latency versus a hypothetical direct Crustdata MCP.

Who it's for

Yalc operators running prospecting from natural language inside Claude Code
Agencies needing one consistent intake API across multiple clients
GTM engineers who already have a Composio account for other toolkits

The Crustdata ecosystem inside Yalc

Crustdata (vendor review)

The vendor side of the same product. Pricing, plans, and direct API context.

→

Alternatives

MCPs to consider instead

ZoomInfo MCP (when available)

Switch when your team is already on ZoomInfo. Crustdata's coverage is broader and fresher.

→

Apollo Composio MCP

Switch when you also need native sequencing in the same vendor. Apollo is shallower on data, deeper on outbound.

→

Predictleads MCP

Use both. Crustdata for static and database queries, Predictleads for live signal events.

→

FAQ

Frequently asked

Why is Crustdata distributed through Composio instead of as a direct MCP?

Composio runs the MCP infrastructure for many SaaS vendors. For Crustdata, this means they don't operate their own MCP server. Composio handles auth, OAuth proxying, and tool exposure. You pay one Composio fee plus your Crustdata fee.

Do I need a Composio account just for Crustdata?

Yes. The Composio API key is required to generate the MCP URL. Composio has a free tier sufficient for piloting.

How does this MCP compare to calling Crustdata's REST API directly?

Functionally equivalent results. The MCP path is more convenient inside Claude Code because the endpoints become native tool calls Claude can compose. The REST API path is better if you're running non agent workflows (cron jobs, batch pipelines).

Can I use this MCP in Claude Desktop?

Yes. The same Composio MCP URL works in Claude Desktop with the desktop app's MCP configuration UI. No code changes required.

Is the data the same as what Yalc pulls via the Crustdata REST API?

Yes. Same backend. Same database. The MCP is just a different transport layer over the same data.

How do I revoke access?

Revoke via Composio's dashboard. Removing the credential there immediately invalidates the MCP URL across every Claude Code session that used it.