Skip to main content
Glama
shuakami

Mail MCP Tool

by shuakami

sendMail

Send emails with recipients, subject, text or HTML content, and attachments through the Mail MCP Tool server for AI-assisted email operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
ccNo
bccNo
subjectYes
textNo
htmlNo
useHtmlNo
attachmentsNo

Implementation Reference

  • Core implementation of sendMail in MailService class using nodemailer Transporter to send email with SMTP.
    async sendMail(mailInfo: MailInfo): Promise<{ success: boolean; messageId?: string; error?: string }> {
      try {
        const mailOptions = {
          from: {
            name: this.config.defaults.fromName,
            address: this.config.defaults.fromEmail,
          },
          to: mailInfo.to,
          cc: mailInfo.cc,
          bcc: mailInfo.bcc,
          subject: mailInfo.subject,
          text: mailInfo.text,
          html: mailInfo.html,
          attachments: mailInfo.attachments,
        };
    
        const info = await this.smtpTransporter.sendMail(mailOptions);
        return { success: true, messageId: info.messageId };
      } catch (error) {
        console.error('发送邮件错误:', error);
        return { success: false, error: error instanceof Error ? error.message : String(error) };
      }
    }
  • MCP tool registration for 'sendMail' using McpServer.tool(), including Zod input schema and async execution handler that prepares MailInfo and calls MailService.sendMail.
    this.server.tool(
      "sendMail",
      {
        to: z.array(z.string()),
        cc: z.string().or(z.array(z.string())).optional(),
        bcc: z.string().or(z.array(z.string())).optional(),
        subject: z.string(),
        text: z.string().optional(),
        html: z.string().optional(),
        useHtml: z.boolean().default(false),
        attachments: z.array(
          z.object({
            filename: z.string(),
            content: z.union([z.string(), z.instanceof(Buffer)]),
            contentType: z.string().optional()
          })
        ).optional()
      },
      async (params) => {
        try {
          // 检查内容是否提供
          if (!params.text && !params.html) {
            return {
              content: [
                { type: "text", text: `邮件内容不能为空,请提供text或html参数。` }
              ]
            };
          }
          
          // 如果指定使用HTML但没有提供HTML内容,自动转换
          if (params.useHtml && !params.html && params.text) {
            // 简单转换文本为HTML
            params.html = params.text
              .split('\n')
              .map(line => `<p>${line}</p>`)
              .join('');
          }
          
          // 处理收件人信息,确保to字段一定存在
          const to = params.to;
          
          const mailInfo: MailInfo = {
            to: to,
            subject: params.subject,
            attachments: params.attachments
          };
          
          // 处理抄送和密送信息
          if (params.cc) {
            mailInfo.cc = typeof params.cc === 'string' ? params.cc : params.cc;
          }
          
          if (params.bcc) {
            mailInfo.bcc = typeof params.bcc === 'string' ? params.bcc : params.bcc;
          }
          
          // 设置邮件内容
          if (params.html || (params.useHtml && params.text)) {
            mailInfo.html = params.html || params.text?.split('\n').map(line => `<p>${line}</p>`).join('');
          } else {
            mailInfo.text = params.text;
          }
          
          const result = await this.mailService.sendMail(mailInfo);
          
          if (result.success) {
            return {
              content: [
                { type: "text", text: `邮件发送成功,消息ID: ${result.messageId}\n\n提示:如果需要等待对方回复,可以使用 waitForReply 工具。` }
              ]
            };
          } else {
            return {
              content: [
                { type: "text", text: `邮件发送失败: ${result.error}` }
              ]
            };
          }
        } catch (error) {
          return {
            content: [
              { type: "text", text: `发送邮件时发生错误: ${error instanceof Error ? error.message : String(error)}` }
            ]
          };
        }
      }
    );
  • Zod schema for sendMail tool input parameters, defining structure for recipients, subject, content, and attachments.
    {
      to: z.array(z.string()),
      cc: z.string().or(z.array(z.string())).optional(),
      bcc: z.string().or(z.array(z.string())).optional(),
      subject: z.string(),
      text: z.string().optional(),
      html: z.string().optional(),
      useHtml: z.boolean().default(false),
      attachments: z.array(
        z.object({
          filename: z.string(),
          content: z.union([z.string(), z.instanceof(Buffer)]),
          contentType: z.string().optional()
        })
      ).optional()
  • TypeScript interface MailInfo defining the input structure passed to the sendMail method.
    export interface MailInfo {
      to: string | string[];
      cc?: string | string[];
      bcc?: string | string[];
      subject: string;
      text?: string;
      html?: string;
      attachments?: Array<{
        filename: string;
        content: string | Buffer;
        contentType?: string;
      }>;
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/shuakami/mcp-mail'

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