o365-Admin MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_CLIENT_ID | Yes | Your Azure AD application client ID | |
| AZURE_TENANT_ID | Yes | Your Azure AD tenant ID | |
| AZURE_CLIENT_SECRET | Yes | Your Azure AD application 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | Returns available skills and resource references. Skills contain API patterns and best practices. Resources contain endpoint-specific documentation for different Microsoft 365 services. |
| read_skillA | Loads a skill or resource reference into context. Use this to learn API patterns before making calls. |
| graph_api_callA | Execute a Microsoft Graph API call. Read the graph-api skill and relevant resource documentation first. |
| powerplatform_api_callC | Execute a Power Platform API call. Read the powerplatform-api skill and relevant resource documentation first. |
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 occupies a distinct role: list_skills discovers available references, read_skill loads a chosen reference, and the two call tools are explicitly separated by target API family (Microsoft Graph vs Power Platform). No two tools plausibly do the same thing.
The skill tools use a clear verb_noun pattern (list_skills, read_skill), but the execution tools are named as target_noun phrases (graph_api_call, powerplatform_api_call) rather than verb-first equivalents. The mixed convention is still readable, but not consistent across the set.
Four tools is a well-scoped size for this server's intended workflow: discover documentation, load documentation, then execute against one of two API families. Every tool has a clear purpose and none feels redundant.
The server covers the full lifecycle implied by its design: list and read the available skills/resources, then make calls to both Microsoft Graph and Power Platform APIs. Since the API-call tools are generic, they can cover any admin operation once the relevant skill is loaded, leaving no obvious dead ends.