ZapSMTP MCP server
Officialby ZapSMTP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAP_SENDER | No | Default From address for sends that omit it; without one, sends require 'from'. | |
| ZAP_API_KEY | Yes | API key for ZapSMTP. Required for stdio usage; not used with --http. | |
| ZAP_BASE_URL | No | ZapSMTP API base URL. | https://api.zapsmtp.com/v1 |
| ZAP_MCP_HOST | No | HTTP address when serving Streamable HTTP. | 127.0.0.1 |
| ZAP_MCP_PORT | No | HTTP port when serving Streamable HTTP. | 3000 |
| ZAP_REPLY_TO | No | Default Reply-To address for sends that omit it. | |
| ZAP_TOOLSETS | No | Comma-separated toolsets to expose, or 'all'. | |
| ZAP_READ_ONLY | No | Set to '1' to expose only tools that change nothing. | |
| ZAP_ALLOWED_RECIPIENT_DOMAINS | No | Comma-separated recipient domains to allow; sends to any other domain are refused. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues