Microsoft Events MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_eventsA | Search Microsoft Events with optional filters and free-text query. IMPORTANT: Before searching, call list_filters first to discover the available filter categories and their exact values. Do not guess filter values — they must match exactly (e.g. "dynamics-365", not "dynamics"). |
| get_event_detailsA | Get details for a specific event by its ID. |
| list_filtersA | List all available filter categories and their exact values with event counts. Call this tool first before using search_events or get_event_stats with filters. It returns the exact category:value pairs that the API accepts. |
| get_event_statsA | Get statistics about events: counts by format, topic, product, region, etc. Uses the API facets for fast, accurate counts (single API call). Use list_filters first to discover valid filter values. |
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 4 tools
Each tool has a clear, distinct purpose: search_events finds events, get_event_details retrieves a single event, list_filters provides valid filter values, and get_event_stats returns aggregate counts. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern with lowercase and underscores: search_events, get_event_details, list_filters, get_event_stats. The naming is uniform and predictable.
With 4 tools, the server is well-scoped for a read-only Microsoft Events API. Each tool serves a necessary function without bloat or redundancy, fitting comfortably within the ideal 3-15 range.
The tool set covers the essential read operations: searching with rich filters, retrieving event details, discovering valid filters, and obtaining statistics. For a read-only events server, there are no obvious gaps or dead ends.