Crustdata MCP

Live

OAUTH 2.0

CRM & SALES

Search

People and company intelligence platform for candidate sourcing, sales prospecting, and talent intelligence. Provides real-time data on professionals...

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Crustdata MCP
agent · Acme Q3
Run
Crustdata Autocomplete Company in Crustdata MCP
S
crustdatamcp_crustdata_autocomplete_company
85ms
Crustdata MCP agent
Get autocomplete suggestions for companydb field values. free — 0 credits consumed. use to discover valid values before .
Sources: Crustdata MCP
crustdatamcpmcp
1 tool call
18:29
Message Claude...

Crustdata MCP tools for AI agents

CALL ANY TOOL
12 tools covering crustdata.
crustdatamcp_crustdata_healthz
Crustdata healthz
Lightweight liveness probe for the Crustdata MCP server itself. Returns {status: 'ok'} when the server is reachable. Does NOT call the Crustdata API or consume credits. Use this when you need to verify the MCP connection is healthy without spending credits.
Parameters
Name
Type
Required
Description
_rationale
string
Optional
Describe the user's intent and why this tool was selected in general terms only; do not include specific field values, names, emails, or other data.
crustdatamcp_crustdata_watch_get
Crustdata watch get
crustdatamcp_crustdata_web_fetch
Crustdata web fetch
crustdatamcp_crustdata_job_search
Crustdata job search
crustdatamcp_crustdata_watch_list
Crustdata watch list
crustdatamcp_crustdata_web_search
Crustdata web search
crustdatamcp_crustdata_watcher_get
Crustdata watcher get
crustdatamcp_crustdata_credit_costs
Crustdata credit costs
crustdatamcp_crustdata_watch_cancel
Crustdata watch cancel
crustdatamcp_crustdata_social_posts
Crustdata social posts
crustdatamcp_crustdata_watch_create
Crustdata watch create
crustdatamcp_crustdata_watch_update
Crustdata watch update
crustdatamcp_crustdata_watcher_list
Crustdata watcher list
crustdatamcp_crustdata_watcher_runs
Crustdata watcher runs
crustdatamcp_crustdata_people_search
Crustdata people search
crustdatamcp_crustdata_credits_check
Crustdata credits check
crustdatamcp_crustdata_company_search
Crustdata company search
crustdatamcp_crustdata_github_enrich
Crustdata github enrich
crustdatamcp_crustdata_watcher_cancel
Crustdata watcher cancel
crustdatamcp_crustdata_people_enrich
Crustdata people enrich
crustdatamcp_crustdata_watcher_create
Crustdata watcher create
crustdatamcp_crustdata_company_enrich
Crustdata company enrich
crustdatamcp_crustdata_watcher_update
Crustdata watcher update
crustdatamcp_crustdata_install_skills
Crustdata install skills
crustdatamcp_crustdata_batch_job_search
Crustdata batch job search
crustdatamcp_crustdata_skill_versions
Crustdata skill versions
crustdatamcp_crustdata_autocomplete_job
Crustdata autocomplete job
crustdatamcp_crustdata_company_identify
Crustdata company identify
crustdatamcp_crustdata_employee_reviews
Crustdata employee reviews
crustdatamcp_crustdata_watcher_simulate
Crustdata watcher simulate
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="crustdatamcp")

mcp = MultiServerMCPClient({
"crustdatamcp": {
"url": "https://mcp.scalekit.com/crustdatamcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "crustdatamcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/crustdatamcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "crustdatamcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/crustdatamcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="crustdatamcp")
# Connect to MCP at https://mcp.scalekit.com/crustdatamcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Search the web for information about companies, people, or topics?
Copy the prompt
Copied
Fetch and extract text content from up to 10 web page URLs in one request?
Advanced
Copy the prompt
Copied
Update an existing watcher subscription?
Copy the prompt
Copied
Simulate a watcher subscription to test your webhook endpoint?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Crustdata MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Crustdata MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Crustdata MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Crustdata MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
GTM and RevOps Teams
Outbound prospecting agent
Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.
GTM and RevOps Teams
CRM AI agent
Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.
GTM and RevOps Teams
Deal intelligence agent
Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Test other agents
See the same per-user auth pattern across other connectors.
SALES
Outbound prospecting agent
Search Apollo for ICP matches, rank them, draft personalised Gmail outreach, and log every send to Google Sheets.
GTM
CRM AI agent
Turn each Granola call transcript into a HubSpot record update, a drafted Gmail follow-up, and a Slack recap.
SALES
Deal intelligence agent
Score Gong call risk with an LLM, cross-reference the Attio record, and DM each owner their at-risk deals in Slack.
GTM
Competitive intelligence briefing agent
Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Crustdata as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Crustdata OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Crustdata?
Yes. Pass a tool name filter to listScopedTools so the research agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Crustdata.

What happens when a user revokes Crustdata access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Whose Crustdata plan do people searches consume?
The authorizing user's. Company autocomplete, people enrichment, and batch job searches draw from that user's quota, keeping sourcing spend attributable per recruiter or rep.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""crustdatamcp"": {
""url"": ""https://mcp.scalekit.com/crustdatamcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.crustdatamcp]
url = ""https://mcp.scalekit.com/crustdatamcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""crustdatamcp"": {
""url"": ""https://mcp.scalekit.com/crustdatamcp"",
""type"": ""http""
}
}
}