What is GTM Tools?

GTM Tools is a monorepo of MCP servers that gives AI agents the building blocks of a modern go-to-market motion. Instead of stitching together a dozen RapidAPI calls, scraping rules, SMTP libraries, and rate-limiting code, you point your agent at a handful of tool calls.

The four servers

ServerSubdomainWhat it does
admin-toolsadmin.gtm-engine.shAPI keys, token balance, Stripe top-ups, auto-reload, invoices
socials-toolssocials.gtm-engine.shLinkedIn automation — search, profiles, companies, posts, jobs, DMs
data-toolsdata.gtm-engine.shSMTP-verified professional email finding (via Reacher)
signals-toolssignals.gtm-engine.shBuying-intent signals — hiring, Trustpilot, social spikes, tech stack

Each server is independent: its own deploy, its own tools.json, its own MCP endpoint. They share one auth boundary (@mcp-tools/shared) and one billing wallet.

Three transports, same tools

TransportWhen to use
MCPStreamable HTTP into Claude Desktop, Cursor, Windsurf, OpenAI agents — agent gets tool list automatically.
RESTServer-side code, batch jobs, anything not MCP-aware. POST /api/v0/{tool_name}.
CLITerminal use, scripting, ad-hoc lookups. gtm-tools <namespace> <command>.

Why build this?

Every GTM team eventually builds the same primitives:

  • A LinkedIn data layer (companies, profiles, employees, posts).
  • An email-finder.
  • A buying-intent signal monitor.
  • An auth + billing layer to stitch them together.

Doing this once is annoying. Doing it for every agent your company deploys is wasteful. GTM Tools standardizes the surface area so the same get_linkedin_profile_url call works whether your agent is built on Claude Desktop, Cursor, or a custom OpenAI loop.

What this is not

  • Not a CRM. There’s no contact storage, deal pipeline, or activity timeline.
  • Not an outbound automation suite. send_linkedin_message exists, but cadence/sequencing logic is your agent’s job.
  • Not an enrichment platform like Clay. The output is per-tool and not warehoused.

If you need any of those, GTM Tools is a layer underneath — call its tools from your agent / CRM / outbound platform.

Open source

The full monorepo is on GitHub. Self-host any subset. admin-tools requires WorkOS + Stripe; the others run without those keys in dev mode.