Microsoft Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_CLIENT_ID | Yes | Your Azure AD client ID | |
| AZURE_TENANT_ID | Yes | Your Azure AD tenant ID | |
| AZURE_CLIENT_SECRET | Yes | Your Azure AD client secret |
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 |
|---|---|
| get_calendar_events_time_specificA | FastMCP tool: Fetch calendar events for a user using Microsoft Graph API. Args: user_id: Microsoft Graph user ID. start: ISO datetime string for start. end: ISO datetime string for end. timezone: IANA timezone (default: UTC). Returns: Dictionary of events or error message. |
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 1 tool
There is only one tool, so there is no possibility of confusing it with another tool. Its purpose of fetching calendar events within a time range is clearly stated.
The tool name follows a clear get_noun structure and is descriptive. However, the 'time_specific' suffix is a bit awkward and there is no broader naming pattern to evaluate with only one tool.
A single tool for a Microsoft Calendar server is far too few for the apparent scope of the domain. Even a focused calendar server would typically need additional event and calendar management operations.
The server only supports fetching events for a time range. It lacks create, update, delete, calendar listing, and event detail operations, making the surface severely incomplete for calendar workflows.