Skip to main content
Glama
closermethod

Outbound Engine MCP

by closermethod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to Outbound Engine MCP

No user-submitted related servers found.

    Related Servers

    • Cold Email & Outreach MCP

      emily397
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to draft evidence-grounded cold-email openers, A/B variants, personalized LinkedIn DMs, and SEO content-gap plans for sales and marketing outreach.
      -

    • MuntuAI MCP

      design-smith
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -

    • coldforge

      Makeph
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables personalized cold email outreach through research, drafting, template management, and deliverability checks, all locally with no required API keys.
      5
      MIT
    • Scrupp MCP server by Wism-Corp

      Scrupp MCP serverofficial

      Wism-Corp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to export leads from LinkedIn, Sales Navigator, and Apollo searches, enrich profiles, look up companies, find decision makers, and discover or verify work emails without writing HTTP calls.
      MIT

    • outreach-crm-mcp

      pensebastian072
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage an outreach CRM via SQLite, including importing contacts from Apollo/Crunchbase, fuzzy matching, seniority ranking, drafting and scoring emails, and tracking sends/replies through pluggable email providers.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct stage or aspect of the outbound workflow: pitch creation, pitch audit, reply interpretation, red-flag detection, pricing, follow-up, and full context. No two tools share the same purpose, even though some operate on similar inputs (replies or pitches).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lowercase snake_case (handle_reply, build_pricing_menu, detect_red_flags, get_full_pack, structure_cold_pitch, audit_cold_message, build_followup_ladder). Verbs are clear and parallel.

    Tool Count5/5

    Seven tools is well-scoped for an outbound engagement engine, covering the core stages without redundancy. The count is within the ideal range and each tool earns its place.

    Completeness5/5

    The tools cover the full lifecycle: structuring a pitch, auditing it, handling replies, detecting red flags, providing pricing guidance, building follow-up ladders, and retrieving the entire engine context. There are no obvious dead ends or missing operations for the server's stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources