MCP Server

MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. All six Mamba Labs GTM signal tools in one MCP server: hiring, tech, ICP, and more. Clay-ready.

What you get

One MCP server that exposes the entire Mamba Labs GTM Suite. Install a single package and get all eleven account-intelligence tools in your MCP client, each wrapping a Mamba Labs actor on Apify and returning Clay-ready flat JSON.

• resolve_company_identity: reconcile name, domain, and LinkedIn URL into one canonical identity with confidence scores
• enrich_company_firmographics: enrich a domain into employee band, industry, HQ, founded year, revenue, logo, and description
• map_company_social_presence: map a domain to LinkedIn, X, Instagram, Facebook, and YouTube URLs and follower counts
• resolve_linkedin_url: resolve a domain or name to a LinkedIn company URL
• scan_gtm_hiring_signals: detect GTM hiring activity from career pages
• detect_gtm_tech_stack: detect CRM, sequencer, and marketing automation tools

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

• resolve_company_identity — at least one of company_name, domain, or linkedin_url, plus skipCache
• enrich_company_firmographics — at least one of domain or domains, plus company_name, batchSize, skipCache
• map_company_social_presence — company_domain or company_name (at least one), plus platforms, includeFollowerCounts, skipCache
• resolve_linkedin_url — company_domain or company_name (at least one)
• scan_gtm_hiring_signals — domain (required), role_filter, ats_slug
• detect_gtm_tech_stack — domain (required), crawl_additional_pages
• scan_job_board_keywords — company_domain (required), role_categories (required), custom_keywords, enable_fallback, previous_roles_detected, previous_run_date
• get_funding_press_signals — domain (required), company_name
• get_company_changes — domain (required), company_name
• aggregate_gtm_signals — company_domain (required), include_summary, explain_mode
• score_icp_fit — company_domain (required), plus template, scoring_config, icp_description (+ llm_api_key, llm_provider), fetch_signals, include_explanation

Configuration and credentials

You will need one environment variable: APIFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or newer - An Apify account with an API token

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — resolve_company_identity, enrich_company_firmographics, map_company_social_presence and 8 more — is a fair guide to whether it matches your workflow. It is maintained by com.mambabuilt; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.