smtp-mcp

Overview Schema Source Related Servers Discussions Admin

Show how this server is configured

get_server_info

Read-onlyIdempotent

Check SMTP server configuration covering endpoint, sender address, allowed recipients, current limits, and sending status to confirm whether emails can be sent.

Instructions

Reports the SMTP endpoint, the fixed sender address, who this server is allowed to write to, the current limits and whether sending is switched on at all. Call this first: it answers "can I send, and to whom" without touching the network.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`from`	Yes
`smtp`	Yes
`limits`	Yes
`can_send`	Yes	The load-bearing fact: both switched on and configured.
`reply_to`	Yes
`configured`	Yes
`attachments`	Yes
`confirmation`	Yes	Whether a person is asked, or a token the model redeems.
`sending_gate`	Yes
`from_is_fixed`	Yes
`sending_enabled`	Yes
`tools_registered`	Yes
`allowed_recipients`	Yes
`elicitation_enabled`	Yes
`audit_log_configured`	Yes
`signature_configured`	Yes
`missing_environment_variables`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Sep 8, 2026

addedOutput schema / properties / reply_to

Added value: +{
+  "anyOf": [
+    {
+      "description": "Where replies are directed. Null means replies go to `from`.",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "can_send",
-  "sending_enabled",
-  "sending_gate",
-  "configured",
-  "missing_environment_variables",
-  "smtp",
-  "from",
-  "from_is_fixed",
-  "allowed_recipients",
-  "limits",
-  "attachments",
-  "signature_configured",
-  "audit_log_configured",
-  "tools_registered",
-  "elicitation_enabled",
-  "confirmation"
-]New value: +[
+  "can_send",
+  "sending_enabled",
+  "sending_gate",
+  "configured",
+  "missing_environment_variables",
+  "smtp",
+  "from",
+  "from_is_fixed",
+  "reply_to",
+  "allowed_recipients",
+  "limits",
+  "attachments",
+  "signature_configured",
+  "audit_log_configured",
+  "tools_registered",
+  "elicitation_enabled",
+  "confirmation"
+]

First observedv0.1.0Sep 5, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds the useful detail that this call does not touch the network, reinforcing the safe, informational nature beyond the annotations.

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 tight sentences deliver all necessary information with no filler. The primary purpose is front-loaded, and the usage hint is concise and actionable.

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

Completeness5/5

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

The description enumerates the key configuration items returned, explains the recommended call order, and notes that it performs no network activity. Combined with the output schema presence, this is complete for an agent to decide when and how to invoke it.

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

Parameters5/5

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

The tool has zero parameters and the schema coverage is 100%, so there is nothing missing. The description fully covers what the tool provides without needing any parameter explanation.

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

Purpose5/5

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

Description clearly states the tool reports server configuration details (SMTP endpoint, sender address, allowed recipients, limits, enabled status) and explicitly frames it as the first call to answer 'can I send, and to whom'. This differentiates it from sibling tools like test_connection.

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

Usage Guidelines5/5

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

Explicitly instructs to call this first and explains it answers whether sending is possible and to whom, without touching the network. This gives clear when-to-use guidance and distinguishes it from network-touching siblings like test_connection or preview_mail.

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

Deploy Server