Email MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP/HTTPS listen address. | 127.0.0.1 |
| MCP_PATH | No | Streamable HTTP path. | /mcp |
| MCP_PORT | No | HTTP/HTTPS port. | 3200 |
| IMAP_HOST | No | IMAP server host. Can be omitted for common providers to auto-fill. | |
| IMAP_PASS | No | IMAP password. If not set, reuses SMTP_PASS. | |
| IMAP_PORT | No | IMAP server port. Can be omitted for common providers to auto-fill. | |
| IMAP_USER | No | IMAP username. If not set, reuses SMTP_USER. | |
| SMTP_HOST | No | SMTP server host. Can be omitted for common providers to auto-fill. | |
| SMTP_PASS | No | SMTP password or authorization code. | |
| SMTP_PORT | No | SMTP server port. Can be omitted for common providers to auto-fill. | |
| SMTP_USER | No | SMTP username (usually the email address). | |
| IMAP_SECURE | No | Whether to use a secure IMAP connection. Set to 'true' or 'false'. Defaults based on provider if omitted. | true |
| MCP_API_KEY | No | Optional. If set, enables Bearer / X-MCP-API-Key authentication. Should be at least 32 bytes in production. | |
| SMTP_SECURE | No | Whether to use a secure SMTP connection. Set to 'true' or 'false'. Defaults based on provider if omitted. | true |
| EMAIL_PROVIDER | No | Email provider mode: 'imap-smtp' or 'gmail-api'. Defaults to 'imap-smtp' if not specified. | |
| GMAIL_CLIENT_ID | No | Google OAuth client ID (required for Gmail API mode). | |
| MCP_CORS_ORIGIN | No | Optional CORS origin. Multiple values can be comma-separated. | |
| MCP_TLS_CA_PATH | No | Optional CA file for client certificate validation (mTLS). | |
| MCP_TRUST_PROXY | No | Set to 'true' to trust the X-Forwarded-Proto header from a trusted proxy. | false |
| MCP_TLS_KEY_PATH | No | Path to the TLS private key file. Must be provided together with MCP_TLS_CERT_PATH for native HTTPS. | |
| MCP_TLS_CERT_PATH | No | Path to the TLS certificate chain file. Must be provided together with MCP_TLS_KEY_PATH for native HTTPS. | |
| DEFAULT_FROM_EMAIL | No | Default sender email address used when sending emails. | |
| GMAIL_ACCESS_TOKEN | No | A valid Gmail access token. Can be used instead of OAuth credentials. | |
| EMAIL_ACCOUNTS_JSON | No | JSON string defining named email accounts. Each account can have provider, from, smtp, imap fields. | |
| GMAIL_CLIENT_SECRET | No | Google OAuth client secret (required for Gmail API mode). | |
| GMAIL_REFRESH_TOKEN | No | Google OAuth refresh token (required for Gmail API mode). | |
| MCP_TLS_MIN_VERSION | No | Minimum TLS version. Allowed values: TLSv1.2 or TLSv1.3. | TLSv1.2 |
| EMAIL_DEFAULT_ACCOUNT | No | Default named account to use when EMAIL_ACCOUNTS_JSON is set. | |
| MCP_TLS_KEY_PASSPHRASE | No | Optional passphrase for the TLS private key. | |
| MCP_TLS_REQUIRE_CLIENT_CERT | No | Whether to require and verify client certificates. Set to 'true' or 'false'. | false |
| EMAIL_ALLOW_INSECURE_TRANSPORT | No | Testing only. Set to 'true' to allow SMTP/IMAP without TLS. | false |
| EMAIL_ALLOW_INVALID_TLS_CERTIFICATES | No | Testing only. Set to 'true' to disable validation of mail server TLS certificates. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send-emailC | 发送邮件 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion between tools.
With a single tool, naming consistency is trivially maintained.
A single send-email tool is too few for an email MCP server, which typically requires additional capabilities like reading, listing, or managing emails.
The tool surface is severely incomplete, covering only sending emails with no support for receiving, listing, or other common email operations.