maillog-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILLOG_API_KEY | Yes | API key used to authenticate with the Maillog API. Get a sandbox key without an account or sign up at https://maillog.nl/signup. |
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_emailA | Send a transactional email through Maillog. The 'from' address must be on a domain verified in the Maillog dashboard, except for sandbox keys, which may only send to the address the sandbox key was issued for. |
| list_emailsA | List emails previously sent through Maillog, newest first, with delivery status and open/click counts. Use this to check whether a message actually went out. |
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 2 tools
send_email and list_emails are clearly distinct: one creates a new email, the other reads previously sent emails. There is no overlap or ambiguity between the two operations.
Both tool names follow a consistent verb_noun snake_case pattern, matching the broader MCP convention. The style is predictable and uniform across the small set.
Two tools is on the thin side for a server, but the pair covers the core send-and-verify workflow implied by the Maillog domain. It is functional yet minimal, so the count is borderline appropriate.
The server covers the essential email send and delivery-check lifecycle with no obvious dead ends. Minor gaps exist, such as no single-email detail lookup or domain management, but the core workflow is workable.