Skip to main content
Glama
mailtrap

MCP Mailtrap Server

Official
by mailtrap

send-email

Destructive

Send transactional emails to single or multiple recipients using Mailtrap's API. Configure sender, recipients, subject, and content while supporting CC, BCC, and HTML formatting for email delivery.

Instructions

Send an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoEmail address of the sender (optional with default)
toYesEmail address(es) of the recipient(s) - can be a single email or array of emails
subjectYesEmail subject line
ccNoOptional CC recipients
bccNoOptional BCC recipients
categoryYesEmail category for tracking
textNoEmail body text
htmlNoOptional HTML version of the email body

Implementation Reference

  • The main handler function for the 'send-email' tool. It constructs and sends an email using the Mailtrap client, handling normalization of recipients, CC/BCC, and error cases.
    async function sendEmail({
      from,
      to,
      subject,
      text,
      cc,
      bcc,
      category,
      html,
    }: SendMailToolRequest): Promise<{ content: any[]; isError?: boolean }> {
      try {
        if (!client) {
          throw new Error("MAILTRAP_API_TOKEN environment variable is required");
        }
    
        if (!html && !text) {
          throw new Error("Either HTML or TEXT body is required");
        }
    
        const fromEmail = from ?? DEFAULT_FROM_EMAIL;
    
        if (!fromEmail) {
          throw new Error(
            "No 'from' email provided and no 'DEFAULT_FROM_EMAIL' email set"
          );
        }
    
        const fromAddress: Address = {
          email: fromEmail,
        };
    
        // Handle both single email and array of emails
        // Normalize inputs: convert to array, trim each email, filter empty strings
        const normalizedToEmails = (Array.isArray(to) ? to : [to])
          .map((email) => email.trim())
          .filter((email) => email.length > 0);
    
        // Validate that we have at least one valid recipient after normalization
        if (normalizedToEmails.length === 0) {
          throw new Error(
            "No valid recipients provided in 'to' field after normalization"
          );
        }
    
        const toAddresses: Address[] = normalizedToEmails.map((email) => ({
          email,
        }));
    
        const emailData: Mail = {
          from: fromAddress,
          to: toAddresses,
          subject,
          text,
          html,
          category,
        };
    
        if (cc && cc.length > 0) {
          const normalizedCcEmails = cc
            .map((email) => email.trim())
            .filter((email) => email.length > 0);
          if (normalizedCcEmails.length > 0) {
            emailData.cc = normalizedCcEmails.map((email) => ({ email }));
          }
        }
        if (bcc && bcc.length > 0) {
          const normalizedBccEmails = bcc
            .map((email) => email.trim())
            .filter((email) => email.length > 0);
          if (normalizedBccEmails.length > 0) {
            emailData.bcc = normalizedBccEmails.map((email) => ({ email }));
          }
        }
    
        const response = await client.send(emailData);
    
        return {
          content: [
            {
              type: "text",
              text: `Email sent successfully to ${toAddresses
                .map((addr) => addr.email)
                .join(", ")}.\nMessage IDs: ${response.message_ids}\nStatus: ${
                response.success ? "Success" : "Failed"
              }`,
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
    
        return {
          content: [
            {
              type: "text",
              text: `Failed to send email: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    }
    
    export default sendEmail;
  • Input schema for the 'send-email' tool, defining properties like to, subject, category (required), from (optional if default set), text/html body, cc/bcc. Dynamically adjusts 'from' required status based on env var.
    const hasDefaultFromEmail = !!process.env.DEFAULT_FROM_EMAIL;
    
    const sendEmailSchema = {
      type: "object",
      properties: {
        from: {
          type: "string",
          format: "email",
          description: hasDefaultFromEmail
            ? "Email address of the sender (optional with default)"
            : "Email address of the sender",
        },
        to: {
          oneOf: [
            {
              type: "string",
              format: "email",
              description: "Single email address",
            },
            {
              type: "array",
              items: {
                type: "string",
                format: "email",
              },
              description: "Array of email addresses",
            },
          ],
          description:
            "Email address(es) of the recipient(s) - can be a single email or array of emails",
        },
        subject: {
          type: "string",
          description: "Email subject line",
        },
        cc: {
          type: "array",
          items: {
            type: "string",
            format: "email",
          },
          description: "Optional CC recipients",
        },
        bcc: {
          type: "array",
          items: {
            type: "string",
            format: "email",
          },
          description: "Optional BCC recipients",
        },
        category: {
          type: "string",
          description: "Email category for tracking",
        },
        text: {
          type: "string",
          description: "Email body text",
        },
        html: {
          type: "string",
          description: "Optional HTML version of the email body",
        },
      },
      required: ["to", "subject", "category"],
      additionalProperties: false,
    };
    
    if (hasDefaultFromEmail) {
      // Make from optional when default is available
      sendEmailSchema.required = sendEmailSchema.required.filter(
        (field: string) => field !== "from"
      );
    }
    
    export default sendEmailSchema;
  • src/server.ts:36-45 (registration)
    Registration of the 'send-email' tool in the tools registry array used by the MCP server, linking the schema and handler, with destructive annotation.
    {
      name: "send-email",
      description:
        "Send an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.",
      inputSchema: sendEmailSchema,
      handler: sendEmail,
      annotations: {
        destructiveHint: true,
      },
    },
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description doesn't contradict the destructiveHint annotation (which indicates this is a write operation). It adds useful context about sending to multiple recipients, but doesn't disclose other behavioral traits like rate limits, authentication requirements, delivery confirmation, or what happens on failure. With annotations covering the destructive nature, the description adds some value but not comprehensive behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with zero waste. The first sentence states the core purpose and API, the second adds a key capability. No redundant information, appropriately front-loaded with the essential action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with 8 parameters and no output schema, the description is minimally adequate. It covers the basic purpose and a key capability, but lacks information about error handling, response format, or integration context that would be helpful given the tool's complexity and destructive nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 8 parameters. The description mentions 'multiple recipients at once' which aligns with the 'to' parameter's array capability, but adds no additional semantic meaning beyond what the schema already provides. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('send an email') and resource ('to your recipient email address'), and specifies the API used ('Mailtrap Email API'). It distinguishes from some siblings like template management tools, but doesn't explicitly differentiate from 'send-sandbox-email' which is a close alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'You can send emails to multiple recipients at once' which provides some context about capability, but offers no guidance on when to use this tool versus alternatives like 'send-sandbox-email' or template-related tools. No explicit when/when-not instructions or prerequisites are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mailtrap/mailtrap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server