ZeptoMail Templates MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOHO_CLIENT_ID | Yes | Zoho OAuth app client ID. Required. | |
| ZOHO_ACCOUNTS_URL | No | Zoho data center (e.g., https://accounts.zoho.eu, https://accounts.zoho.in). | https://accounts.zoho.com |
| ZEPTOMAIL_MCP_PORT | No | For hosted mode, the port to listen on (e.g., 3006). | |
| ZOHO_CLIENT_SECRET | Yes | Zoho OAuth app client secret. Required. | |
| ZOHO_REFRESH_TOKEN | No | Long-lived token; the server mints 1-hour access tokens from it. Required for stdio mode (default). | |
| ZEPTOMAIL_API_BASE_URL | No | ZeptoMail API base URL. | https://api.zeptomail.com/v1.1 |
| ZEPTOMAIL_MCP_TRANSPORT | No | Set to 'http' to enable hosted OAuth mode. | stdio |
| ZEPTOMAIL_MCP_SERVER_URL | No | For hosted mode, the public HTTPS URL of this MCP server (e.g., https://mcp.example.com). | |
| ZEPTOMAIL_MCP_TOKEN_STORE | No | For hosted mode, path to a persistent token store file (e.g., /var/lib/zeptomail-mcp/tokens.json). | |
| ZEPTOMAIL_MCP_ALLOW_WRITES | No | Set to 'true' to enable create/update/delete tools. | false |
| ZEPTOMAIL_MCP_ALLOWED_AGENT_KEYS | No | Comma-separated list of allowed mailagent_key values. Defaults to all agents. |
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 |
|---|---|
| zeptomail_list_agentsA | List accessible Agents in the ZeptoMail account. Returns each Agent name and exact mailagent_key (Agent alias). Always use the returned key for template tools; do not guess Agent identifiers. |
| zeptomail_list_templatesA | List templates in one explicit ZeptoMail Agent. Use zeptomail_list_agents first and pass the exact returned mailagent_key. |
| zeptomail_find_templatesA | Search template name, alias and subject. Omit agentKey to search across every accessible Agent; provide agentKey to restrict the search to one Agent. Results always include the owning Agent. |
| zeptomail_get_templateA | Fetch one complete template from one explicit Agent by exact template key. Always call this before updating or deleting. |
| zeptomail_export_templatesA | Fetch every full template (HTML body, text body, subject, alias, attachments metadata) from one explicit Agent and return them as a single JSON dump. Read-only. Use when the caller wants to back up an Agent templates to local files; the caller writes the files itself — this tool returns the data, it does not write to disk. |
| zeptomail_create_templateA | Create a template in one explicit Agent. Requires agentKey plus expectedAgentName from a fresh zeptomail_list_agents call, server writes enabled, and confirm=true. |
| zeptomail_update_templateA | Partially update a template in one explicit Agent. Requires expectedAgentName and expectedModifiedTime from fresh reads so a stale or wrong-Agent edit is rejected. Requires writes enabled and confirm=true. |
| zeptomail_delete_templateA | Permanently delete a template from one explicit Agent. Requires expectedAgentName, expectedTemplateName, and expectedModifiedTime from fresh reads. Requires writes enabled and confirm=true. |
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 8 tools
Each tool targets a distinct resource and action: agents vs templates, and list/search/get/export/create/update/delete are clearly separated. Even the similar list_templates and find_templates are disambiguated by one being an enumeration and the other being a search across name, alias, and subject.
All tool names use the consistent zeptomail_ prefix followed by verb_noun snake_case, such as zeptomail_list_agents and zeptomail_update_template. The naming pattern is uniform and predictable across the entire set.
Eight tools is well-scoped for a ZeptoMail template management server. Each tool covers a necessary operation without redundancy or bloat, and the count is within the ideal range for a focused domain server.
The tool surface provides full lifecycle coverage for templates: list, search, get, export, create, update, and delete. Agent enumeration supports the required context for template operations, so agents can accomplish end-to-end template management without dead ends.