mcp-emailjs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMAILJS_PUBLIC_KEY | Yes | Your EmailJS public key | |
| EMAILJS_SERVICE_ID | Yes | Your EmailJS service ID | |
| EMAILJS_PRIVATE_KEY | No | Your EmailJS private key (required for get_email_history) |
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_emailB | Send an email using an EmailJS template. Credentials can be passed as parameters or read from EMAILJS_SERVICE_ID, EMAILJS_PUBLIC_KEY, and EMAILJS_PRIVATE_KEY environment variables. |
| validate_configA | Validate EmailJS credentials and template ID. WARNING: EmailJS has no dry-run endpoint, so this performs a real send with empty template params — it consumes send quota and may deliver an email if the template has no required variables. Returns a clear message indicating which part of the configuration is invalid. |
| get_email_historyA | Retrieve the history of emails sent via EmailJS. Requires EMAILJS_PUBLIC_KEY and EMAILJS_PRIVATE_KEY (accessToken) for authentication. |
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 3 tools
Each tool serves a distinct purpose: retrieving history, sending emails, and validating configuration. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (get_email_history, send_email, validate_config).
Three tools is well-scoped for an email service, covering the core operations without unnecessary bloat.
The set covers sending, history, and config validation. Minor gap: lacks template management or cancellation, but core workflow is complete.