Skip to main content
Glama
bugzy-ai

Resend MCP Server

by bugzy-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Resend MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Email Service

      Marary
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables sending emails (including mass emailing), querying, updating, and canceling delayed emails via the Resend API.
      -

    • Resend MCP Server

      universal-mcp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending emails and managing email delivery through Resend's API, allowing users to compose and send emails using natural language.
      1
      MIT

    • MCP Email Server

      Code2Hack18
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients like Cursor to send emails via Resend, supporting multiple recipients, subjects, and HTML bodies, with configuration through environment variables.
      1,020 npm
      MIT

    • SendLayer MCP Server

      gyrationtechs
      F
      license
      B
      quality
      Not graded
      maintenance
      Enables sending emails and managing webhooks through the SendLayer API. Supports plain text and HTML emails with attachments, CC/BCC recipients, and webhook event management for email delivery tracking.
      5
      -

    • Resend MCP Server

      pontusab
      A
      license
      Not graded
      quality
      D
      maintenance
      Allows sending emails through the Resend service using a standardized Model Context Protocol (MCP) interface, with TypeScript support.
      12,155 npm
      6
      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

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose for sending emails.

    Naming Consistency5/5

    The tool name follows a consistent verb_noun pattern (resend_send_email), and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.

    Tool Count2/5

    A single tool for an email server is too few for the apparent scope, as it lacks basic operations like listing emails, checking status, or managing templates. This limits functionality and may cause agent failures.

    Completeness2/5

    The tool surface is severely incomplete for an email domain; it only supports sending emails without any read, update, delete, or management capabilities. This creates significant gaps that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources