ForIT Microsoft Graph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MS365_MCP_CLIENT_ID | No | Azure AD app client ID (optional) | |
| MS365_MCP_TENANT_ID | No | Azure AD tenant ID (default: common) | common |
| MS365_MCP_CLIENT_SECRET | No | Client secret for confidential apps |
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 |
|---|---|
| loginA | Authenticate with Microsoft using device code flow |
| logoutB | Log out from Microsoft account |
| verify-loginA | Check current Microsoft authentication status |
| list-accountsB | List all available Microsoft accounts |
| select-accountC | Select a specific Microsoft account to use |
| remove-accountC | Remove a Microsoft account from the cache |
| graph-requestA | Execute a raw Microsoft Graph API request. Supports any Graph API endpoint. Can target specific account without switching. Documentation:
|
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 7 tools
Each tool has a clearly distinct purpose with no overlap: graph-request handles API calls, list-accounts enumerates accounts, login/logout manage authentication, remove-account deletes cached accounts, select-account switches contexts, and verify-login checks status. The tools cover different aspects of the Microsoft Graph workflow without ambiguity.
All tool names follow a consistent snake_case pattern with clear verb-noun combinations (e.g., list-accounts, select-account, verify-login). The naming is uniform across all seven tools, making them predictable and easy to understand for an agent.
With 7 tools, the server is well-scoped for its purpose of interacting with Microsoft Graph. It provides essential operations for authentication, account management, and API requests, with each tool serving a necessary function without bloat or redundancy.
The tool set offers complete coverage for the domain: graph-request enables all CRUD operations via the Graph API, while the other tools handle authentication, account selection, and status verification. There are no obvious gaps, allowing agents to perform end-to-end workflows seamlessly.