stormgtm-mcp
Related Servers
Alternatives to stormgtm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to find leads, read buying signals, write and send email and LinkedIn outreach, handle replies, and report results, with built-in safety gates, approvals, limits, and compliance controls.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables automated Gmail lead nurturing campaigns with intelligent follow-ups, response tracking, and 24/7 operation. Supports CSV-based contact management, template personalization, and real-time monitoring for enterprise-scale email outreach.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send and receive email with enforced security policies, scoped mailboxes, and human approval for external sending.1MIT

PumpGTM MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to find intent-signaling buyers and run LinkedIn, email, and X outreach from connected accounts while respecting platform limits. Every reply is handed back to a human for approval or decision.1MIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.-
- AlicenseNot gradedqualityFmaintenanceValidates email deliverability, assesses domain credibility, and scores B2B leads from A-F to help prioritize outreach, with batch processing and a free tier.MIT
TDQS
Scored across 24 tools
Most tools target distinct resources: lead discovery (find_leads), deliverability (check_lead/check_batch/qualify_radar_leads), sending (send_email/reply), sequences, and inbox actions are well separated. Minor overlap exists between whoami and credits (both expose credit balance) and among the several lead-checking tools, but descriptions clarify the boundaries.
Actions consistently use verb_noun (find_leads, send_email, create_sequence, archive_threads, mark_spam) and informational/query tools use noun phrases (batch_status, credits, domain_health, sequence_status), which is a coherent convention. The lone outlier is 'whoami' (camelCase with no separator), a minor deviation from the otherwise uniform snake_case.
24 tools is on the heavier side but justified given the server spans several sub-domains: account/credits, domains, lead discovery, deliverability checking, sending, sequences, and inbox management. Each tool covers a distinct capability, though the set could be slightly consolidated (e.g. whoami/credits).
Coverage is strong across the outreach lifecycle: discovery, qualification, batch review, sending, sequences, outcome reporting, and full inbox management (read, reply, mark, archive, spam). Minor gaps remain—no way to pause/update or delete an entire sequence, and no general listing for non-Radar leads saved by find_leads—but core workflows are complete.