MCP SERVERResolve a company to one canonical identity, read its hiring, tech-stack, funding and AI signals, score it against your ICP, and push what survives into a sequencer.
LABSCO SUMMARY
The suite is read-only apart from push_leads_to_sequencer, which adds leads to an Instantly or Smartlead campaign — and even that takes dry_run, a minimum ICP score and deduplication against what the campaign already holds, so the first pass can be a dress rehearsal. The output shape is the other deliberate decision: flat, one row per company, which is what lets these calls drop straight into an enrichment table instead of being reshaped first. Cost sits on the Apify side, one actor run per call against your token, so point aggregate_gtm_signals or get_company_changes at a shortlist rather than a whole list.
A single MCP server over the Mamba Labs account-intelligence actors on Apify. Each tool wraps one actor and answers in flat, Clay-ready JSON, covering a full go-to-market pass: resolve the identity, enrich the account, detect buying signals, score fit, then send the survivors on. The package is a thin client — the work runs on Apify against your own token.
Node.js 18 or newer, run over stdio as npx -y @mambalabsdev/mcp-gtm-suite. APIFY_TOKEN is required — from console.apify.com/account/integrations — and every call runs an Apify actor and consumes Apify credits. score_icp_fit needs an llm_api_key only when the ICP is given in plain English rather than as a template or scoring_config. push_leads_to_sequencer additionally takes the sequencer's own api_key and a campaign_id. MIT.
One command plus a key — npx -y @mambalabsdev/mcp-gtm-suite, then supply credentials
USE CASES
Give it whatever you have — a name, a domain, a LinkedIn URL — and get one canonical identity back with a confidence score on each part and the method that produced it.
Firmographics from the company's own structured data, social presence with follower counts, and any funding or executive news the wires carried.
Hiring activity across the major applicant tracking systems, plus the CRM and sequencer they already run, combined into one score with a recommended action.
Separate the companies that mention AI from the ones running it, and from the ones whose pricing page actually charges for it.
A verdict on whether there is a deliberate outbound program, with the sending stack and the lookalike domains behind the call.
Score against your ICP, then push only what clears the bar into Instantly or Smartlead — deduplicated against the campaign, and dry-run first if the mapping is new.
Monitor each domain and get back only the hiring, tech, funding, firmographic or social changes since the previous run.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
aggregate_gtm_signalsAggregate a company's GTM signals into one composite score. Runs hiring and tech-stack detection in one call and returns a composite score, recommended action, and optional summary as a flat, Clay-ready JSON row. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
detect_ai_toolingGiven a company domain, determine how far that company has gone with AI. Returns an ai_maturity tier of none, declared (says AI but nothing observable is running), deployed (AI tooling is live on the site), or commercialized (the pricing page charges for AI via credits, tokens, an add-on, an AI-named plan, or a per-outcome price), plus the detected AI vendors, validated llms.txt status, robots.txt AI-crawler policy, and the evidence behind the verdict. A domain behind a bot challenge returns blocked=true at low confidence rather than a false negative. Returns flat, Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.
detect_gtm_tech_stackDetect which GTM tools a company uses from its public website. Returns CRM, sequencer, and marketing automation signals with per-tool boolean flags as a flat, Clay-ready JSON row. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
enrich_company_firmographicsEnrich a company domain into structured firmographics: employee band, industry, HQ, founded year, revenue estimate, logo, and description, with source provenance. Parsed from the company's schema.org/Organization JSON-LD and HTML meta tags and returned as a flat, Clay-ready JSON row with a source_signals array and a data_completeness score. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
fingerprint_outbound_infrastructureGiven a company domain, determine whether that company runs cold email outbound and on what stack. Returns a runs_outbound verdict of program (a deliberate cold outbound setup), light (one weak signal), none, or unknown, with the evidence behind it. The strongest signal is the lookalike sending domains a real program leaves behind: domains like getcompany.com or company-mail.com that carry their own mail and redirect back to the primary site. Also returns the inbox provider (Google Workspace, Microsoft 365 and others) for the primary domain and each sending domain, any detected sending platform (Outreach, Salesloft, Lemlist, Instantly, Smartlead, Apollo and more), registration clusters showing sending domains bought on the same day, cold email infrastructure vendors, and SPF, DKIM and DMARC posture. Sending platform recall is partial by design: sequencers that connect over OAuth to a customer's own mailbox leave no DNS trace, so an empty sending_platforms means little while a populated one is solid. Public DNS and HTTP redirects only. Returns flat, Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.
get_company_changesMonitor a company domain for changes across hiring, tech stack, funding, firmographics, and social since the last run. Returns only what changed as typed change events in flat, Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
get_funding_press_signalsScan Google News and PR wires for funding rounds, executive moves, product launches, and acquisitions at any company domain. Returns deduplicated, dated events in flat Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
map_company_social_presenceMap a company's social media presence across LinkedIn, X, Instagram, Facebook, and YouTube. Returns profile URLs and follower counts in flat Clay-ready JSON. Profiles are discovered from the company's own homepage links, a web search fallback, and pattern guessing, then validated against the company. Follower counts are extracted where public; X is URL-only (its count needs login) and Instagram and Facebook counts are best-effort. Provide at least one of company_domain or company_name. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
push_leads_to_sequencerPush enriched lead rows into an existing Instantly or Smartlead campaign. Maps common Clay column names onto each sequencer's own field names, optionally drops leads below a minimum ICP score, optionally deduplicates against the leads already in the destination campaign, and sends the rest in batches. Returns one flat summary row: how many leads were received, dropped for having no usable email, dropped by the ICP gate, dropped as duplicates, eligible, actually created by the sequencer, skipped by the sequencer, and failed, plus the vendor's own error message per failed address. The campaign must already exist; this does not create campaigns or write sequence copy. Set dry_run true to get back the exact request payload that would be sent without creating a single lead and without being charged, which is the safe way to check a mapping against a new campaign. Billing is per lead the sequencer confirms it created, so gated, duplicate, skipped, failed and dry-run leads are all free. Instantly uses API v2 and needs a v2 key; Smartlead uses API v1. Requires an APIFY_TOKEN and consumes Apify credits. This WRITES to your sequencer campaign unless dry_run is true.
resolve_company_identityResolve any combination of company name, domain, or LinkedIn URL into one canonical company identity: the name, primary domain, and LinkedIn company URL, each with a 0-100 confidence score plus an overall score and a match method. Cross-checks the inputs you give it, resolves the ones you do not, and flags conflicts (a domain and a LinkedIn slug that disagree) instead of merging them. Provide at least one of company_name, domain, or linkedin_url. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
resolve_linkedin_urlResolve a company domain or name to its LinkedIn company URL with a confidence score, firmographics, and social links as a flat, Clay-ready JSON row. Provide at least one of company_domain or company_name. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
scan_gtm_hiring_signalsScan company career pages to detect GTM hiring activity. Returns sales, marketing, and revenue operations job postings across Greenhouse, Lever, and Ashby as a flat, Clay-ready JSON row. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
scan_job_board_keywordsScan a company's job board for roles in chosen categories across Greenhouse, Lever, Ashby, Workday, and Rippling. Returns matched role counts and titles per category as a flat, Clay-ready JSON row. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
score_icp_fitScore a company against your ideal customer profile (ICP) using weighted signals. Returns a 0 to 100 icp_score, an A to D icp_tier, and a per-signal breakdown as a flat, Clay-ready JSON row. Define your ICP with a template, scoring_config, or plain-English icp_description (which requires llm_api_key). Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
track_publication_cadenceGiven a company domain, measure how much long-form work that company publishes and whether the rate is rising or falling. Returns post counts for the last 30 days, 90 days and 12 months, a monthly average, and a cadence_trend of accelerating, steady, declining, dormant or unknown, with the percent change behind it. The trend compares the last 90 days against the prior 275 days, both normalized to posts per month. Also returns the blog URL, the format mix (blog posts, guides, reports, case studies, whitepapers, podcasts, videos, press releases, research), the number of distinct bylines, and how the post list was discovered. This measures EDITORIAL output volume, not product changelogs: a release feed is detected and rejected rather than counted. Publication dates are read from the post pages, because sitemap lastmod was measured to be a modification date running later than publication by a median of 151 to 1653 days. When a site's date field tracks edits rather than publication, date_source_reliable comes back false and every count is nulled rather than reported wrong, so read that field before quoting a number. Counts are a census when the archive fits the page budget and a scaled even sample otherwise, flagged by counts_are_estimate. Public sitemaps, feeds and pages only. Returns flat, Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.
BEFORE YOU INSTALL
15 tools when we connected. The project advertises 21, but resolve_legal_entity, classify_contact, audit_agent_accessibility, map_company_event_presence, monitor_public_awards and capture_linkedin_posts_and_commenters do not register, likely documented ahead of the bundled 1.8.0 server.
The documented client runs the server on your machine.
CONTEXT COST
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @mambalabsdev/mcp-gtm-suite{
"mcpServers": {
"mamba-gtm-suite": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-gtm-suite"
],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}MCP servers
mambalabsdevmambalabsdevmambalabsdevmambalabsdev