Introduction
Your AI agent can write outreach, schedule meetings, and qualify leads. But the moment it needs real data — a prospect’s LinkedIn URL, a verified email, evidence that a company is hiring SDRs, follower spikes on TikTok — it stalls. Stitching together RapidAPI calls, scraping rules, SMTP verifiers, and rate-limit logic is a project in itself.
GTM Tools is a monorepo of MCP servers that exposes that stack as a handful of tool calls. Every tool is metered in tokens, billed centrally, and reachable via MCP, REST, or CLI — so you focus on the agent loop, not the plumbing.
What is GTM Tools?
GTM Tools is a single MCP service exposing five tool categories:
Everything ships behind a single host: api.gtm-tools.sh/mcp for MCP, api.gtm-tools.sh/api/v0/{tool} for REST. One auth boundary, one billing wallet. New accounts get 100 free tokens to start.
(gtm-tools.sh itself is the docs site you’re reading — the API lives under the api. subdomain.)
Three ways in
MCP
Point an MCP-compatible client (Claude Desktop, Cursor, Windsurf) at the server URL with your bearer token. Tools appear in your agent’s tool list automatically.
What your agent can do
1. Get auth and manage billing
get_api_key gets a key via email verification. get_token_balance returns the wallet state, buy_tokens tops up via card (5 minimum), set_auto_reload configures auto top-up when the balance dips below a threshold, and list_invoices returns the purchase history. New accounts get 100 free tokens.
2. Find and act on LinkedIn
The most common starting point is get_linkedin_company_url — feed it a domain and it returns the company’s LinkedIn page. From there, list_linkedin_company_employees lists the workforce with boolean title filters ("(CEO OR CTO OR Founder) NOT intern"), get_linkedin_profile_url gets a profile URL from name + company, and get_linkedin_profile / get_linkedin_company get the full structured records. Once you’ve found the right person, send_linkedin_invitation and send_linkedin_message close the loop. The write and personal-data tools run through a logged-in session shared by the browser extension; list_connected_linkedin_accounts shows which sessions are connected.
3. Engage on Reddit
21 tools covering the full engagement loop. Discover: search_reddit_posts (keyword surveillance), list_subreddit_posts (daily hot/new/rising), search_reddit_subreddits (shortlist communities), get_subreddit_about (the rule-compliance gate every Reddit playbook flags as the #1 shadowban trigger). Evaluate: get_reddit_post (post + full comment tree), get_reddit_user (karma, account age, verified flags), list_reddit_user_posts (posting history — is this actually our ICP?). Engage: create_reddit_comment (reply to post or comment), create_reddit_post (submit), vote_reddit (up/down/clear), send_reddit_message (DM via Reddit’s Matrix-based Chat — works for every account, including the post-rollout cohort that can’t receive legacy PMs). Follow up: follow_reddit_post (notifications on new comments), save_reddit_thing with optional CRM-stage category label, list_reddit_saved, list_reddit_inbox. Organize: subscribe_reddit_subreddit (bulk sub/unsub), list_reddit_subscriptions, plus custom feeds (multireddits) via list_reddit_custom_feeds, list_reddit_custom_feed_posts, create_reddit_custom_feed — one feed per ICP / campaign, then daily monitoring reads the merged stream in one call. All write tools (and the gate-bypassing reads) run on a pooled session from the browser extension; list_connected_reddit_accounts shows which accounts are connected. See the Results Ranking Optimization guide for the should-I-reply gate and anti-spam style rules.
4. Verify professional emails
get_email takes a name + domain and returns a deliverable email. It generates every common pattern (first@, first.last@, flast@, etc.) and verifies each against the domain’s mail server via SMTP — no mail actually sent. Catch-all domains are flagged in the response so your agent knows when to trust the result.
5. Detect buying signals
detect_signal runs every signal in one call. The individual detectors live alongside it: signal_socials_spike (Instagram/TikTok follower jumps), signal_hiring_role / signal_hiring_support / signal_hiring_sales_rep / signal_hiring_sales_leadership / signal_hiring_sales_rep_repost (job-board scans, including reposted SDR roles as a churn signal), signal_trustpilot_negative_reviews / signal_trustpilot_negative_support_reviews / signal_trustpilot_positive_reviews, and signal_technologies_identified (stack detection on the website). set_signals_order / get_signals_order configure execution order.
Quick example
Same flow from the CLI: