exchange-ai-connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXCHANGE_AI_TIMEZONE | No | Optional: override auto-detected timezone, e.g. Asia/Bangkok | |
| EXCHANGE_AI_AUTHORITY | No | Optional: pin to a specific tenant, e.g. https://login.microsoftonline.com/<tenant-id> | |
| EXCHANGE_AI_CLIENT_ID | Yes | Your app's client ID from Microsoft Entra ID registration |
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 messages in a mail folder. Read-only. |
| read_emailB | Read one message in full. Read-only. |
| read_threadC | Read all messages in a conversation, oldest first. Read-only. |
| send_emailA | Send or reply to an email. IRREVERSIBLE — the client must confirm before allowing. |
| list_eventsB | List upcoming calendar events, soonest first. Read-only. |
| read_eventC | Read one calendar event in full. Read-only. |
| check_availabilityA | Free/busy over a window. Times are naive local, e.g. '2026-07-02T14:00:00'. attendees defaults to just you. Read-only. |
| create_eventA | Create a calendar event; emails invites to attendees. Times are naive local, e.g. '2026-07-02T14:00:00'. IRREVERSIBLE — the client must confirm before allowing. |
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 operation within either the calendar or email domain, with no overlapping purposes. check_availability, create_event, list_events, and read_event are clearly separate; similarly for email tools.
All tools follow a consistent verb_noun pattern using snake_case (e.g., check_availability, list_emails). No mixing of conventions or ambiguous verbs.
With 8 tools covering both email and calendar operations, the count is well-scoped for the connector's purpose. Each tool serves a clear function without superfluous entries.
The tool surface covers essential read and create operations but lacks update and delete for calendar events, and email deletion or folder management. These are notable gaps for a full lifecycle.