mcp-ecc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for SSE server (default: 3000) | |
| MCP_STORAGE_FILE | No | Path to the storage file (default: ./config.json) | |
| MCP_ENCRYPTION_KEY | No | Master encryption key for encrypting token credentials via AES-256-GCM. If omitted, credentials will be stored in plain JSON. |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticate_accountB | Authenticate and register a Google, Microsoft, Zoho, or IMAP/SMTP account. Supports headless OAuth (device code flow) with custom client/tenant configurations. |
| email_list_emailsC | Search or view recent emails. |
| email_get_emailC | Fetch the body and metadata of a specific email. |
| email_send_emailC | Send a plain text or HTML email. |
| email_manage_emailB | Archive, mark read/unread, or star an email. |
| email_delete_emailC | Move email to Trash or delete permanently. |
| calendar_list_eventsB | View scheduled events/appointments within a time range. |
| calendar_create_eventC | Create a calendar event. |
| calendar_update_eventC | Modify an existing calendar event. |
| calendar_delete_eventC | Delete/remove a calendar event. |
| contacts_search_contactsC | Find contact entries by name or query term. |
| contacts_create_contactC | Inject a new contact into the address book. |
| contacts_delete_contactC | Remove a contact entry. |
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 13 tools
Tools are clearly grouped by domain (calendar, contacts, email) with distinct actions per domain. There is no overlap in functionality, and each tool serves a unique purpose.
All tools follow a consistent 'domain_action' pattern (e.g., calendar_create_event, email_send_email) with only 'authenticate_account' lacking a prefix, which is acceptable as a singleton.
13 tools cover authentication, calendar, contacts, and email comprehensively without being overwhelming. The count is well-scoped for a multi-domain server.
Calendar and email have full CRUD-like coverage; contacts lack an update tool, which is a minor gap. Overall, the tool surface covers core workflows effectively.