Skip to main content
Glama
sendhustle-mcp

sendhustle-mcp

Related Servers

Alternatives to sendhustle-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      267 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to send emails, manage campaigns, subscribers, templates, and domains via the SendCraft email API.
      26
      3 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      AI-powered email assistant that enables sending, parsing, and managing emails using natural language. Provides 4 tools (smart_email, parse_email_intent, send_email, email_chat) with SSE/stdio transport support.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage email newsletters and contacts via Resend, including sending broadcasts to segments, managing subscribers in bulk, scheduling campaigns, and tracking delivery status using human-friendly identifiers.
      14,032 npm
      5
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with the Inbound Email API to manage domains, endpoints, and email communications. Users can send or schedule emails, manage webhooks, and retrieve email threads through natural language commands.
      14
      2
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 111 tools

    Disambiguation4/5

    Almost every tool maps to a distinct resource+action, and the descriptions are specific. A few pairs could be confused—create_event (definition) vs send_event, and get_email_attachment vs get_received_email_attachment—but the names plus descriptions largely disambiguate them.

    Naming Consistency4/5

    Tools overwhelmingly follow a snake_case verb_noun pattern (create_domain, list_contacts, update_campaign). Minor inconsistency: retrieve_email instead of get_email, and several synonyms for similar actions (stop/cancel/delete, verify/check) slightly soften the pattern.

    Tool Count1/5

    111 tools is an extreme count; even if each maps to a distinct endpoint, the set is far beyond the well-scoped range and will burden an agent's selection. This aligns with the 50+ overgrown category.

    Completeness5/5

    The surface covers full lifecycles for domains, audiences, contacts, properties, segments, topics, templates, campaigns, sent/received emails, automations, events, webhooks, API keys, logs, and polls. There are no obvious dead ends or missing CRUD operations for the apparent email-platform domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues