Skip to main content
Glama
Wh1isper

MCP Email Server

by Wh1isper
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

send_email

Send an email from a specified account with attachments, HTML, CC/BCC, and reply threading. Receive per-recipient delivery status to confirm success or failure.

Instructions

Send one email using the specified account. Supports reply threading. Partial or ambiguous SMTP delivery reports per-recipient succeeded/failed/unknown status and reports the independent Sent-copy outcome separately; ambiguous effects are not retried automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoA list of CC email addresses.
bccNoA list of BCC email addresses.
bodyYesThe body of the email.
htmlNoWhether to send the email as HTML (True) or plain text (False).
subjectYesThe subject of the email.
reply_toNoEmail address to set as the Reply-To header. When set, email clients will reply to this address instead of the From address.
recipientsYesA list of recipient email addresses.
referencesNoSpace-separated Message-IDs for the thread chain. Simple IDs may be bare or bracketed; bare IDs gain RFC angle brackets during composition. Usually includes in_reply_to plus ancestors.
attachmentsNoA list of file paths to attach. Relative paths are resolved against the server process working directory; absolute paths are recommended.
in_reply_toNoMessage-ID of the email being replied to. Simple IDs may be bare or bracketed; bare IDs gain RFC angle brackets during composition.
account_nameYesThe name of the email account to send from.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.5.2
    • changedInput schema / properties / in_reply_to / description
      Previous value: -"Message-ID of the email being replied to. Enables proper threading in email clients."New value: +"Message-ID of the email being replied to. Simple IDs may be bare or bracketed; bare IDs gain RFC angle brackets during composition."
    • changedInput schema / properties / references / description
      Previous value: -"Space-separated Message-IDs for the thread chain. Usually includes in_reply_to plus ancestors."New value: +"Space-separated Message-IDs for the thread chain. Simple IDs may be bare or bracketed; bare IDs gain RFC angle brackets during composition. Usually includes in_reply_to plus ancestors."
  2. Addedv1.1.1
  3. Removedv1.0.1
  4. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / reply_to
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Email address to set as the Reply-To header. When set, email clients will reply to this address instead of the From address.",
+  "title": "Reply To"
+}
  5. Addedv0.8.0
  6. Removedv0.7.0
  7. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / attachments
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A list of absolute file paths to attach to the email. Supports common file types (documents, images, archives, etc.).",
+  "title": "Attachments"
+}
    • addedInput schema / properties / html
      Added value: +{
+  "default": false,
+  "description": "Whether to send the email as HTML (True) or plain text (False).",
+  "title": "Html",
+  "type": "boolean"
+}
    • addedInput schema / properties / in_reply_to
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Message-ID of the email being replied to. Enables proper threading in email clients.",
+  "title": "In Reply To"
+}
    • addedInput schema / properties / references
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Space-separated Message-IDs for the thread chain. Usually includes in_reply_to plus ancestors.",
+  "title": "References"
+}
    • changedOutput schema / properties / result / type
      Previous value: -"null"New value: +"string"
  8. First observed

TDQS

A3.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing critical runtime behavior: per-recipient succeeded/failed/unknown status, a separate Sent-copy outcome, and no automatic retry of ambiguous effects. It also notes reply threading support. These details are essential for correctly interpreting results and avoiding duplicate sends.

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

Conciseness4/5

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

The description is compact and front-loaded with the primary action in the first sentence. The second sentence is dense but packs valuable behavioral facts. Minor awkward phrasing ('reports per-recipient succeeded/failed/unknown status') prevents a perfect score.

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?

The description covers core behavior and delivery-report semantics, but omits usage context such as account validation, allow-list restrictions, and when to prefer forward_email or save_to_mailbox. Given the tool's complexity and the presence of an output schema and detailed parameter descriptions, these gaps leave the definition only moderately complete.

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?

The input schema provides 100% coverage with detailed descriptions for all 11 parameters, including attachment path resolution and RFC bracket behavior for message-IDs. The tool description adds no additional parameter-level information, so the baseline of 3 applies.

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 verb and resource: 'Send one email using the specified account.' It also mentions reply threading, which adds useful specificity. However, it does not explicitly distinguish this from the sibling forward_email, which also ultimately sends messages, so it falls just short of full differentiation.

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 provides no guidance on when to use send_email versus forward_email or save_to_mailbox, and does not mention prerequisites such as validating the account via list_available_accounts or checking recipient/sender allow-lists. Usage context is left entirely to inference.

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/Wh1isper/mcp-email-server'

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