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) |
Capabilities
Features and capabilities supported by this server
| 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 by performing a test call. 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ElizioMartins/mcp-emailjs'
If you have feedback or need assistance with the MCP directory API, please join our Discord server