Gtm Signals Aggregator MCP server

GTM Signals Aggregator MCP Server

An MCP server that rolls a company's go-to-market signals into one composite score. It wraps the Mamba Labs GTM Signals Aggregator actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

• What it does
• Quick start
• Prerequisites
• Example prompts
• Inputs
• Output
• Example output
• Features
• Full actor documentation
• Mamba Labs GTM Suite
• License

What it does

Give it a company domain and it runs hiring-signal and tech-stack detection together, then returns a single composite GTM score, a recommended action, and an optional plain-English summary. One call, one row, ready to drop into Clay, a CRM, or an AI agent workflow. All of the analysis runs on Apify. This package is a thin client that calls the actor and hands back the result.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

{
  "mcpServers": {
    "mamba-gtm-signals": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-gtm-signals-aggregator"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The aggregategtmsignals tool will be available.

Prerequisites

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

Example prompts

• "Give me the overall GTM signal score for stripe.com."
• "How strong a GTM target is openai.com? Aggregate their signals."
• "Score figma.com on hiring and tech stack, and explain why."
• "Pull the composite GTM signal for datadoghq.com with a summary."

Inputs

• company_domain (required): the bare company domain, no https:// and no trailing slash. Example: stripe.com
• sources (optional): which signals to aggregate: hiring, techstack, funding, events, workplace. Default ["hiring", "techstack"]. Each extra source is one more sub actor run on your own Apify account. The composite score is normalized over the sources you selected.
• includesummary (optional): include a plain-English gtmsignal_summary in the output.
• explain_mode (optional): if true, the summary becomes a longer, more detailed explanation.

Output

Shortened. The full README is on GitHub.