Skip to main content
Glama
Sign In
Microsoft Graph MCP Server

Microsoft Graph MCP Server

by marlonluo2018
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

auth

Authenticate with Microsoft Graph by starting a login flow, checking status, completing browser verification, or logging out.

Instructions

Manage authentication with Microsoft Graph. Four simple actions:

• 'start' - Start login flow, returns verification URL and code to enter in browser • 'complete' - Complete login after browser authentication (auto-loads device code) • 'check_status' - Check auth status: returns authenticated or need login • 'logout' - Clear all authentication tokens

WHEN AUTHENTICATION NEEDED: Always try 'check_status' FIRST. If it fails (no token or expired), then call 'start'.

WORKFLOW:

  1. Call auth action='start' → get URL and code

  2. Open URL in browser, enter the code, complete Microsoft login

  3. Call auth action='complete' → authentication finished

AUTO-REFRESH: Access tokens auto-refresh when expired (no user action needed). Refresh tokens are valid for ~90 days.

Returns:

  • check_status: {status: string, authenticated: boolean, message: string}

  • start: {status: string, verification_uri: string, user_code: string, message: string}

  • complete: {status: string, authenticated: boolean, message: string}

  • logout: {status: string, authenticated: false, message: string}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction: 'start' to begin login (get URL/code), 'complete' to finish login after browser auth, 'check_status' to check authentication status, 'logout' to sign out

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses token auto-refresh, 90-day refresh token validity, and return formats for each action. No annotations provided, so description carries full burden; slightly missing error state details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with bullet points, sections, and front-loaded summary. Every sentence adds value despite length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description provides explicit return formats for each action. Covers entire workflow and authentication lifecycle.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds workflow context for each enum value. Baseline 3 plus extra value from detailed action descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Manage authentication with Microsoft Graph' and enumerates four actions. This distinguishes it from sibling tools dealing with emails, events, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'Always try check_status first', then start if needed, with a clear step-by-step workflow. No ambiguity about when to use each action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools