GetMailer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GETMAILER_API_KEY | Yes | Your GetMailer API key | |
| GETMAILER_API_URL | No | Custom API URL | https://getmailer.app |
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 |
|---|---|
| send_emailC | Send a transactional email via GetMailer |
| list_emailsB | List sent emails with status information |
| get_emailB | Get details of a specific email including delivery events |
| list_templatesB | List available email templates |
| create_templateC | Create a new email template |
| list_domainsB | List verified sending domains |
| add_domainB | Add a new sending domain (returns DNS records to configure) |
| verify_domainC | Check if a domain has been verified |
| get_analyticsC | Get email analytics and statistics |
| list_suppressionB | List suppressed email addresses (bounced, complained, or manually added) |
| add_to_suppressionC | Add email addresses to the suppression list |
| create_batchC | Create a batch email job to send to multiple recipients |
| list_batchesB | List batch email jobs |
| get_batchC | Get batch job status and progress |
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 14 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the email sending domain. For example, add_domain vs verify_domain handle different aspects of domain management, while send_email vs create_batch address different email sending scenarios. No tools appear to overlap in functionality.
All tools follow a consistent verb_noun naming pattern throughout (e.g., add_domain, create_batch, get_analytics, list_templates). The verbs are appropriate and predictable (add, create, get, list, send, verify), and the snake_case convention is uniformly applied across all 14 tools.
With 14 tools, this server is well-scoped for an email sending service, covering domain management, email sending (transactional and batch), templates, analytics, and suppression lists. Each tool earns its place by addressing a distinct aspect of the workflow, avoiding both excessive bloat and critical omissions.
The tool set provides complete CRUD/lifecycle coverage for the email sending domain. It includes creation (add_domain, create_batch, create_template), retrieval (get_analytics, get_batch, get_email, list_* tools), and operational actions (send_email, verify_domain, add_to_suppression). No obvious gaps exist; agents can manage the full email workflow from setup to analytics.