Skip to main content
Glama
day0ops

mcp-graph-me-tool

by day0ops

mcp-graph-me-tool

A minimal Streamable HTTP MCP server exposing one tool, graph_me, which calls Microsoft Graph's GET /me with the caller's bearer token and returns the signed-in user's profile.

It's the backend half of a Microsoft Entra ID On-Behalf-Of (OBO) token exchange demo: a gateway (e.g. agentgateway) sits in front of this server, validates the caller's Entra token, exchanges it for a Graph-scoped token via Entra's own token endpoint, and forwards the request here with the exchanged token substituted for Authorization. This server does not perform any exchange or validation itself - it only relays whatever bearer token it's handed to Graph.

What it does

sequenceDiagram
    participant Client as MCP Client
    participant AGW as Gateway (OBO exchange)
    participant Tool as mcp-graph-me-tool
    participant Graph as Microsoft Graph

    Client->>AGW: tools/call graph_me + user's Entra token
    AGW->>AGW: exchange for a Graph-scoped token
    AGW->>Tool: tools/call graph_me + exchanged token
    Tool->>Graph: GET /v1.0/me + exchanged token
    Graph-->>Tool: profile
    Tool-->>AGW: tool result
    AGW-->>Client: tool result
  • graph_me - no arguments. Reads the Authorization header off the incoming HTTP request and calls https://graph.microsoft.com/v1.0/me with it. Returns the profile JSON on success, or {"error": "Graph API returned <status>", "detail": "<Graph's own error body>"} on failure (including when no Authorization header is present at all).

  • GET /healthz - plain 200 ok liveness/readiness check.

Each HTTP request gets a fresh McpServer instance built from that request's own Authorization header (see buildServer() in server.js) - there is no session or connection state held between requests.

Related MCP server: MCPAuthFuncapp

Running locally

npm install
npm start
# listening on :8080 (override with PORT)
curl localhost:8080/healthz
# ok

Development

npm test   # node --check server.js (syntax check)

Wiring into agentgateway

Deploy this image behind a plain EnterpriseAgentgatewayBackend/HTTPRoute pointing at port 8080, protocol: StreamableHTTP, path: /mcp, then apply an oauthTokenExchange policy (grantType: JwtBearer) on that route to perform the Entra OBO exchange before requests reach this server. See docs.solo.io's Entra OBO guide for the full walkthrough.

License

Apache License 2.0 - see LICENSE.

A
license - permissive license
-
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • F
    license
    -
    quality
    D
    maintenance
    A secure Model Context Protocol backend service built on Azure Functions that provides authenticated access to Microsoft Graph API. It leverages Azure Active Directory and APIM to enable secure tool discovery and user context management through the OAuth On-Behalf-Of flow.
  • F
    license
    -
    quality
    D
    maintenance
    Implements the on-behalf-of flow with Entra ID to enable authorized calls to Microsoft Graph API via MCP tools.
    9

View all related MCP servers

Related MCP Connectors

  • The personal context layer for AI: your profile and files, read by any MCP client over OAuth.

  • Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.

  • MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/day0ops/mcp-graph-me-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server