Skip to main content
Glama
marginsystems

stormgtm-mcp

Related Servers

Alternatives to stormgtm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to a hosted multichannel B2B outbound engine for LinkedIn messaging, cold email sequencing, and pipeline management, including campaign reads and prospect research. Write actions that send, launch, enroll, or spend credits require chat confirmation before completing.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to research and score leads against industry ICP templates, draft cold emails, and gate every draft through CAN-SPAM and deliverability checks before a human approves it. Nothing is sent by default, and each step is recorded in an append-only audit log showing why a lead was contacted.
      399 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      2
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to send and receive email with enforced security policies, scoped mailboxes, and human approval for external sending.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      3
      MIT

    TDQS

    A3.6/5.0

    Scored across 24 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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).

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues