MCP Aruba Email & Calendar Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAP_HOST | No | IMAP server host for Aruba | imaps.aruba.it |
| IMAP_PORT | No | IMAP server port for Aruba | 993 |
| SMTP_HOST | No | SMTP server host for Aruba | smtps.aruba.it |
| SMTP_PORT | No | SMTP server port for Aruba | 465 |
| CALDAV_URL | Yes | The CalDAV URL for calendar synchronization (e.g., https://syncdav.aruba.it/calendars/tua_email@aruba.it/) | |
| IMAP_PASSWORD | Yes | Aruba email password used for IMAP authentication | |
| IMAP_USERNAME | Yes | Aruba email address used for IMAP authentication | |
| CALDAV_PASSWORD | Yes | Aruba email password used for CalDAV authentication | |
| CALDAV_USERNAME | Yes | Aruba email address used for CalDAV authentication |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_emailsB | List emails from the specified folder. |
| read_emailA | Read the full content of a specific email. |
| search_emailsB | Search emails by subject or body content. |
| send_emailB | Send an email via SMTP. |
| check_bounced_emailsA | Check for bounced or failed email delivery notifications. |
| set_email_signatureA | Create and save a professional email signature with optional photo and colors. |
| get_email_signatureC | Get a saved email signature. |
| list_email_signaturesB | List all saved email signatures. |
| create_calendar_eventA | Create a new calendar event. |
| list_calendar_eventsB | List calendar events within a date range. |
| accept_calendar_eventA | Accept a calendar event invitation. |
| decline_calendar_eventA | Decline a calendar event invitation. |
| tentative_calendar_eventA | Mark a calendar event as tentative (maybe attending). |
| delete_calendar_eventB | Delete a calendar event. |
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 with no significant overlap. Calendar tools handle specific actions (accept, decline, tentative, create, delete, list), email tools cover distinct operations (list, read, search, send, check bounces, manage signatures), and the separation between email and calendar domains is clear. An agent can easily differentiate between tools like list_emails and search_emails or accept_calendar_event and decline_calendar_event.
All tool names follow a consistent verb_noun pattern with snake_case throughout. Calendar tools use verbs like accept, decline, create, delete, list, tentative paired with 'calendar_event', while email tools use verbs like list, read, search, send, check, get, set paired with 'email' or related nouns (e.g., 'email_signature', 'bounced_emails'). This uniformity makes the tool set predictable and easy to navigate.
With 14 tools, the count is well-suited for the server's dual-domain purpose of email and calendar management. It provides comprehensive coverage without being overwhelming, balancing core operations (e.g., CRUD for events, email listing/sending) with specialized utilities (e.g., signature management, bounce checking). This scope aligns with typical productivity server expectations.
The tool set offers strong coverage for both email and calendar domains, including full lifecycle management for calendar events (create, list, accept/decline/tentative, delete) and essential email operations (send, list, read, search, bounce checking, signature management). Minor gaps exist, such as no tools for updating calendar events or managing email folders, but agents can work around these with the provided tools without significant hindrance.