Tratto MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRATTO_API_KEY | Yes | API key from app.tratto.email/settings/api-keys |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailB | Send a transactional email via Tratto |
| list_emailsA | List sent emails from Tratto with optional status filter |
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 have completely distinct purposes: one initiates an outgoing email, the other retrieves a list of previously sent emails. There is no overlap or ambiguity between the two.
Both tool names follow the consistent verb_noun pattern using snake_case: send_email and list_emails. The naming is predictable and uniform.
With only 2 tools, the server feels thin for an email-related service. While the core actions of sending and listing are covered, the small number of tools is borderline and may leave users wanting more functionality.
The server provides the fundamental lifecycle of sending and listing emails, but lacks a dedicated get_email or delete_email operation. This minor gap could be worked around if list_emails returns full details, but a single-email lookup is a common need.