Lokka MCP Server

Lokka is a model-context-protocol server for the Microsoft Graph and Azure RM APIs that allows you to query and manage your Azure and Microsoft 365

Local serverstdio

What is the Lokka MCP server?

Lokka is a model-context-protocol server for the Microsoft Graph and Azure RM APIs that allows you to query and manage your Azure and Microsoft 365 tenants with AI. That is what the lokka mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • Per — request override**: You can still specify graphApiVersion parameter in individual requests (unless USE_GRAPH_BETA=false)
  • Input — - apiType (string): Type of Microsoft API to query. Options: 'graph' for Microsoft Graph (Entra) or 'azure' for Azure Resource Management
  • Returns — Results from the Azure or Graph API call
  • Tools — 1. Lokka-Microsoft - Call Microsoft Graph & Azure APIs. Supports querying Azure and Microsoft 365 tenants. Updates are also supported if permissions

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: TENANT_ID, CLIENT_ID, USE_INTERACTIVE, CERTIFICATE_PATH, CERTIFICATE_PASSWORD, USE_CERTIFICATE, CLIENT_SECRET, USE_CLIENT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lokka's toolset — Per, Input, Returns and 1 more — is a fair guide to whether it matches your workflow. It is maintained by merill; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Perrequest override**: You can still specify graphApiVersion parameter in individual requests (unless USE_GRAPH_BETA=false)
Input- apiType (string): Type of Microsoft API to query. Options: 'graph' for Microsoft Graph (Entra) or 'azure' for Azure Resource Management.
ReturnsResults from the Azure or Graph API call.
Tools1. Lokka-Microsoft - Call Microsoft Graph & Azure APIs. Supports querying Azure and Microsoft 365 tenants. Updates are also supported if permissions are provided. - Input: - apiType (string): Type of Microsoft API to que

How to install the Lokka MCP server

{
  "mcpServers": {
    "Lokka-Microsoft": {
      "command": "npx",
      "args": ["-y", "@merill/lokka"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
TENANT_IDConfiguration value read at startup.Optional
CLIENT_IDConfiguration value read at startup.Optional
USE_INTERACTIVEConfiguration value read at startup.Optional
CERTIFICATE_PATHFilesystem location the server is allowed to use.Optional
CERTIFICATE_PASSWORDConfiguration value read at startup.Optional
USE_CERTIFICATEConfiguration value read at startup.Optional
CLIENT_SECRETCredential the server authenticates with.Yes
USE_CLIENT_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Lokka to Per.
  • Use Lokka to Input.
  • Use Lokka to Returns.

Frequently asked questions

It connects Lokka to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Per, Input, Returns, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Lokka directly.