Outlook Meetings Scheduler MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | Authentication mode: 'interactive' (default), 'client_credentials', or 'client_provided_token' | interactive |
| CLIENT_ID | No | Azure AD Application (Client) ID | |
| TENANT_ID | No | Azure AD Tenant ID | common |
| USER_EMAIL | No | Email address of the user whose calendar to access | |
| ACCESS_TOKEN | No | Pre-acquired access token | |
| REDIRECT_URI | No | Custom redirect URI | http://localhost |
| CLIENT_SECRET | No | Azure AD Application Client Secret | |
| TOKEN_EXPIRES_ON | No | Token expiration date in ISO format (e.g., 2025-10-03T12:00:00Z) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find-personC | Find a person's email address by their name |
| create-eventC | Create a calendar event using Microsoft Graph API |
| create-event-with-attendeesC | Create a calendar event with attendees using Microsoft Graph API |
| get-eventC | Get details of a calendar event by its ID |
| list-eventsC | List calendar events with optional filtering |
| update-eventC | Update an existing calendar event |
| update-event-attendeesC | Add or remove attendees from a calendar event |
| delete-eventC | 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 8 tools
Most tools have distinct purposes, but there is some overlap between create-event and create-event-with-attendees, which could cause confusion about when to use each. The other tools are clearly differentiated by their specific actions on calendar events or person lookup.
All tool names follow a consistent verb-noun pattern using snake_case, such as create-event, delete-event, and update-event-attendees. This predictability makes it easy for agents to understand and select the appropriate tool.
With 8 tools, the server is well-scoped for scheduling meetings in Outlook, covering essential CRUD operations for events, attendee management, and person lookup. Each tool serves a clear purpose without being overwhelming.
The tool set provides complete coverage for the domain, including create, read, update, and delete for events, plus specific tools for managing attendees and finding people. There are no obvious gaps that would hinder agent workflows in scheduling meetings.