Dead Simple Email
Server Details
Give an agent its own inbox: send, receive, and pull signup codes from real email.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
14 toolscreate_inboxInspect
Create a new email inbox. Returns the inbox details including the email address.
Args:
display_name: Friendly name for the inbox (e.g. "Support Bot")
tags: Comma-separated tags (e.g. "support,production")
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | ||
| display_name | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
delete_inboxInspect
Delete an inbox and all its messages.
Args:
inbox_id: The inbox ID to delete
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
forward_messageInspect
Forward a message to new recipients.
Args:
inbox_id: The inbox containing the message
message_id: The message ID to forward
to: Recipient email address (comma-separated for multiple)
body: Optional additional text to include
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| body | No | ||
| inbox_id | Yes | ||
| message_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_usageInspect
Get account usage metrics: inboxes, emails sent/received, plan limits.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_verification_codeInspect
Wait for a verification/OTP email and return the extracted code.
Waits for the next new inbound email, then returns the auto-extracted
verification code (and any magic link). Perfect for autonomous sign-ups.
Args:
inbox_id: The inbox to watch
from_contains: Only match senders containing this text (optional)
timeout_seconds: Max seconds to wait (default 60)
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | ||
| from_contains | No | ||
| timeout_seconds | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_verification_linkInspect
Wait for an email and return the extracted magic link / verification URL.
Args:
inbox_id: The inbox to watch
from_contains: Only match senders containing this text (optional)
timeout_seconds: Max seconds to wait (default 60)
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | ||
| from_contains | No | ||
| timeout_seconds | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_inboxesInspect
List all email inboxes in the account.
Args:
limit: Maximum number of inboxes to return (default 20)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_threadsInspect
List conversation threads in an inbox.
Args:
inbox_id: The inbox to list threads for
limit: Maximum number of threads to return (default 10)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| inbox_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
read_messageInspect
Read a single message with full body content.
Args:
inbox_id: The inbox containing the message
message_id: The message ID to read
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | ||
| message_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
read_messagesInspect
Read recent messages in an inbox.
Args:
inbox_id: The inbox to read from
limit: Maximum number of messages to return (default 10)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| inbox_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
read_threadInspect
Read all messages in a conversation thread.
Args:
inbox_id: The inbox containing the thread
thread_id: The thread ID to read
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | ||
| thread_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
reply_to_messageInspect
Reply to a message. Threading headers are set automatically.
Args:
inbox_id: The inbox containing the message
message_id: The message ID to reply to
body: Reply body (plain text)
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| inbox_id | Yes | ||
| message_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
send_emailInspect
Send an email from an inbox.
Args:
inbox_id: The inbox to send from
to: Recipient email address (comma-separated for multiple)
subject: Email subject line
body: Email body (plain text)
cc: CC recipients (comma-separated, optional)
bcc: BCC recipients (comma-separated, optional)
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | ||
| to | Yes | ||
| bcc | No | ||
| body | Yes | ||
| subject | Yes | ||
| inbox_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
wait_for_emailInspect
Block until a NEW inbound email arrives in the inbox, then return it.
Use for signup/verification flows: trigger the action that sends the email,
then call this to receive it. Only emails arriving after this call count.
Args:
inbox_id: The inbox to watch
from_contains: Only match senders containing this text (optional)
subject_contains: Only match subjects containing this text (optional)
timeout_seconds: Max seconds to wait (default 60)
| Name | Required | Description | Default |
|---|---|---|---|
| inbox_id | Yes | ||
| from_contains | No | ||
| timeout_seconds | No | ||
| subject_contains | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!