What features does Microsoft 365 MCP server provide?

Q: What features does Microsoft 365 MCP server provide?

Lokka-Microsoft API Tool: Calls Microsoft Graph and Azure APIs; supports querying and updating Azure and Microsoft 365 tenants when permissions are provided.. Natural language MCP client integration: Allows Claude Desktop or any MCP client to issue natural language commands to perform Graph/Azure actions.. Multiple authentication methods: Supports Interactive Auth, App-Only Auth with Certificate, and App-Only Auth with Client Secret.. Client-provided token mode: Supports token-based authentication where the MCP client provides Microsoft Graph tokens.. Token management tools: New tools set-access-token, get-auth-status, and add-graph-permission for managing tokens and permissions.. Graph API version control: Default to beta; can force v1.0 with USE_GRAPH_BETA=false; per-request overrides via graphApiVersion.. Environment variable configuration: Configure TENANT_ID, CLIENT_ID, CLIENT_SECRET, CERTIFICATE_PATH, CERTIFICATE_PASSWORD, USE_INTERACTIVE, USE_CERTIFICATE, USE_CLIENT_TOKEN, and related settings.. Installation/usage integration: Provides configuration examples for Claude Desktop and VS Code installations, including one-click VS Code install options.

Microsoft 365 MCP Server 2025: Features & Setup Guide

Overview

Lokka is a Model Context Protocol (MCP) server that acts as a bridge to the Microsoft Graph and Azure Resource Manager APIs, enabling AI-powered querying and management of Microsoft 365 and Azure tenants. It supports Claude Desktop or any MCP client to interpret natural language commands and translate them into Graph/Azure API calls. The server exposes a single tool, Lokka-Microsoft, to call Graph and Azure APIs with inputs such as apiType, path, method, apiVersion, subscriptionId, queryParams, and body, returning API results. Authentication is flexible: you can use interactive user login, app-only authentication with either a PEM certificate or client secret, or client-provided tokens. Configuration is environment-driven via TENANT_ID, CLIENT_ID, CLIENT_SECRET, CERTIFICATE_PATH, CERTIFICATE_PASSWORD, USE_INTERACTIVE, USE_CERTIFICATE, USE_CLIENT_TOKEN, REDIRECT_URI, ACCESS_TOKEN, and USE_GRAPH_BETA. New tools add token management (set-access-token, get-auth-status, add-graph-permission) and graph API version control (default beta, force v1.0 with USE_GRAPH_BETA=false, plus per-request overrides). The README also includes installation hints and examples for usage with Claude Desktop and VS Code.

Features

Lokka-Microsoft API Tool

Calls Microsoft Graph and Azure APIs; supports querying and updating Azure and Microsoft 365 tenants when permissions are provided.

Natural language MCP client integration

Allows Claude Desktop or any MCP client to issue natural language commands to perform Graph/Azure actions.

Multiple authentication methods

Supports Interactive Auth, App-Only Auth with Certificate, and App-Only Auth with Client Secret.

Client-provided token mode

Supports token-based authentication where the MCP client provides Microsoft Graph tokens.

Token management tools

New tools set-access-token, get-auth-status, and add-graph-permission for managing tokens and permissions.

Graph API version control

Default to beta; can force v1.0 with USE_GRAPH_BETA=false; per-request overrides via graphApiVersion.

Environment variable configuration

Configure TENANT_ID, CLIENT_ID, CLIENT_SECRET, CERTIFICATE_PATH, CERTIFICATE_PASSWORD, USE_INTERACTIVE, USE_CERTIFICATE, USE_CLIENT_TOKEN, and related settings.

Installation/usage integration

Provides configuration examples for Claude Desktop and VS Code installations, including one-click VS Code install options.