graphdo-ts
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAPHDO_DEBUG | No | Enable debug logging (true/false) | false |
| GRAPHDO_CLIENT_ID | No | Azure AD (Entra ID) application client ID | b073490b-a1a2-4bb8-9d83-00bb5c15fcfd |
| GRAPHDO_GRAPH_URL | No | Override Graph API base URL | https://graph.microsoft.com/v1.0 |
| GRAPHDO_TENANT_ID | No | Azure AD tenant ID (common, organizations, consumers, or a GUID) | common |
| GRAPHDO_CONFIG_DIR | No | Override config directory | |
| GRAPHDO_ACCESS_TOKEN | No | Skip MSAL auth and use a static Bearer token |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Sign in to Microsoft Graph. Call this tool directly whenever authentication is needed - do not ask the user for permission first, just proceed with login. Opens a browser for interactive sign-in. Once signed in, all other tools work automatically. |
| logoutA | Sign out of Microsoft Graph and clear all cached tokens. After logging out, the login tool must be used to re-authenticate. |
| auth_statusA | Check current authentication status, logged-in user, configured todo list, granted scopes, and server version. A good first tool to call when diagnosing issues or understanding what is set up. |
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 3 tools
Each tool addresses a distinct aspect of the authentication lifecycle: login for signing in, logout for signing out, and auth_status for checking the current state. There is no overlap or ambiguity between them.
Tool names are short and predictable, but 'auth_status' is a noun phrase while 'login' and 'logout' are verbs. The pattern is mostly consistent, though 'get_auth_status' would improve verb-noun consistency.
Three tools is the minimum needed to cover the authentication lifecycle, and each tool serves an essential role. The scope is narrow but well-filled, with no unnecessary additions.
The set covers the full authentication domain: login, logout, and status checking. There are no missing operations for the stated purpose, making the surface complete for authentication management.