Server facts
mcp-gtm-suite
Project
- Author
- mambalabsdev
- Repository
- github.com/mambalabsdev/mcp-gtm-suite
- License
- MIT
- Category
- Search & Web Data
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- Apify
- clay
- gtm
- sales intelligence
- suite
Overview
Account research in mcp-gtm-suite can start with a company name, domain, or LinkedIn URL, then move through identity matching, firmographic enrichment, and social profile discovery. Hiring scans, website technology detection, funding news, and change monitoring provide signals for account assessment. Scoring tools combine hiring and technology findings or evaluate a company against a supplied ideal customer profile. Other tools examine AI adoption, outbound email infrastructure, publishing frequency, conference participation, and legal registration. Results use flat JSON suited to Clay workflows, while Apify actors perform the underlying work.
The suite also supports contact-title classification, public award research, LinkedIn post collection, and audits of how accessible websites are to AI agents. Coverage limits matter: public LinkedIn comments are incomplete, event discovery reflects what companies publish, and legal-entity matching can return no result. For activation, enriched leads can be sent to existing Instantly or Smartlead campaigns, with optional score filtering and duplicate checks. This operation writes to the destination unless dry-run mode is enabled; it does not build campaigns or draft sequences. The package runs on Node.js through stdio and requires an Apify token, with tool usage consuming Apify credits.
mcp-gtm-suite setup notes
- mcp-gtm-suite records stdio only; confirm a network transport upstream before planning remote access.