MCP SERVERAsk questions about your Microsoft 365 and Azure tenant in plain language — and put a policy in front of the model before it starts writing to it.
LABSCO SUMMARY
Because the surface is a path and a method rather than a fixed tool list, coverage is never the problem and blast radius is: guardrails answer that directly by restricting which methods, which API paths and even which resource ids a model may touch, and lokka-get-guardrails lets you read the policy in force before trusting a session. Two practical notes: Graph calls default to the beta version, which is worth pinning with USE_GRAPH_BETA=false on a production tenant, and permission errors are recoverable in place — get-auth-status shows the scopes you hold and add-graph-permission asks for more.
A single call onto the Microsoft Graph and Azure Resource Management APIs, wrapped in tenant connection management and a guardrails policy. Anything Graph can reach — Entra, Intune, Teams, SharePoint — is reachable by path, and Azure resources come through the same tool.
A Microsoft Entra tenant and an account with the Graph or Azure permissions for whatever you ask it to do — Lokka can only do what those permissions allow. Node v22.10 or higher, started as npx -y @merill/lokka. Interactive sign-in with the default Lokka app needs no variables; a custom app takes TENANT_ID, CLIENT_ID and USE_INTERACTIVE=true, with REDIRECT_URI defaulting to http://localhost:3000. App-only runs either on CLIENT_SECRET, or on USE_CERTIFICATE=true with CERTIFICATE_PATH pointing at a PEM file and CERTIFICATE_PASSWORD if it is encrypted. USE_CLIENT_TOKEN=true switches to tokens supplied by the client instead.
One command — npx -y @merill/lokka
USE CASES
Query the policy collections directly by Graph path, page through the whole set, and filter server-side rather than reading pages of results.
Check which scopes the session holds, request the missing one through a fresh sign-in, then make the write — instead of finding out mid-task that it was read-only.
Read the guardrails in force — allowed methods, API allow and deny rules, resource allowlists — and open the guardrails UI to tighten them before you start.
See which tenant connections are signed in, switch to the other one by name, and run the same query again.
Point the same tool at Azure Resource Management with the subscription and API version, so tenant and subscription questions are answered in one session.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add-graph-permissionRequest additional Microsoft Graph permission scopes by performing a fresh interactive sign-in. This tool only works in interactive authentication mode and should be used if any Graph API call returns a permission denied error.
get-auth-statusCheck the current authentication status and mode of the MCP Server and also returns the current graph permission scopes of the access token for the current session.
lokka-add-cert-connectionInternal: add an app-only connection that authenticates with a client certificate (PEM). Used by the Lokka connections app UI.
lokka-add-sp-connectionInternal: add a service principal (client credentials) connection to a Microsoft tenant. Used by the Lokka connections app UI.
lokka-add-user-connectionInternal: sign into a Microsoft tenant interactively (browser) and add it as a Lokka connection. Used by the Lokka connections app UI.
lokka-connect-created-appInternal: complete sign-in for an app created by lokka-create-app. Returns { connected:false } while the new app is still replicating through the directory — poll until connected. Used by the Lokka connections app UI.
lokka-consent-permissionsInternal: request or remove Microsoft Graph delegated permission scopes for the active connection. Used by the Lokka permissions app UI.
lokka-create-appInternal: create a new Entra app registration in the active user's tenant — adds a client secret or auto-generated certificate, grants the requested Graph application permissions, and stores the credential. Does NOT sign in (poll lokka-connect-created-app afterwards). Used by the Lokka connections app UI.
lokka-get-guardrailsGet the guardrails (user-set policy) currently in effect for model tool calls on the active connection: which HTTP methods are allowed, the API allow/deny rules, and any per-resource id allowlists. Read-only — guardrails can only be changed by the user in the Lokka Guardrails app (open-lokka-guardrails). Direct user runs from Graph Explorer are not blocked by guardrails.
lokka-get-guardrails-configInternal: full guardrails config plus the connected tenants and resource presets, for the Guardrails app editor.
lokka-get-permissionsInternal: get the Microsoft Graph permissions (scopes/roles) currently granted to Lokka's active connection. Used by the Lokka permissions app UI.
lokka-grant-app-permissionsInternal: grant or remove Microsoft Graph application permissions on an app-only connection, using a signed-in user/admin connection in the same tenant. Used by the Lokka connections app UI.
lokka-list-connectionsList Lokka's signed-in Microsoft tenant connections and which one is active. Use this to see which tenants are available before switching, or when the user asks which tenant/account Lokka is using.
Lokka-MicrosoftA versatile tool to interact with Microsoft APIs including Microsoft Graph (Entra) and Azure Resource Management. IMPORTANT: For Graph API GET requests using advanced query parameters ($filter, $count, $search, $orderby), you are ADVISED to set 'consistencyLevel: "eventual"'. NOTE: Results are specific to Lokka's active tenant connection (named in each result). If the user switches connections/tenants, earlier results in this conversation are stale — re-run the query instead of reusing previous answers. If a call fails because the user is not signed in, IMMEDIATELY call 'open-lokka-connections' to show them the sign-in dialog instead of only telling them to sign in.
lokka-reconnect-connectionInternal: re-acquire a fresh token for a connection (user connections re-run interactive sign-in to pick up newly consented scopes; service principals rebuild from the stored secret/certificate to pick up newly granted app roles). Used by the Lokka connections app UI.
lokka-remove-connectionInternal: remove a Lokka tenant connection. Used by the Lokka connections app UI.
lokka-remove-guardrails-tenantInternal: remove a tenant's guardrails rule so it reverts to Global only. Used by the Guardrails app.
lokka-search-directoryInternal: search the active connection's directory for items in a collection (e.g. groups, users) by name, for the Guardrails resource picker. Read-only; not subject to guardrails.
lokka-set-active-connectionInternal: switch Lokka's active tenant connection. Used by the Lokka connections app UI.
lokka-set-connection-labelInternal: set a friendly display label for a connection (empty clears it). Used by the Lokka connections app UI.
lokka-set-guardrails-enabledInternal: enable or disable Guardrails enforcement. Used by the Guardrails app. When disabled, Lokka allows every request through without method, API path, or resource guardrail checks.
lokka-set-guardrails-scopeInternal: replace the guardrails policy for a scope ('global' or a tenant id). Used by the Guardrails app.
lokka-update-app-credentialInternal: replace an app-only connection's credential with a new client secret or certificate, then reconnect. Used by the Lokka connections app UI.
open-graph-explorerOpen the interactive Lokka Graph explorer UI for the user. Call this whenever the user asks to open, show, or launch Lokka, the Lokka app, or the Graph explorer (e.g. 'open lokka', 'show me the graph explorer'), or wants to explore Microsoft Graph interactively without running a specific query first. Optionally pre-fills a request path for the user to start from.
open-lokka-connectionsOpen the Lokka connections manager UI for the user. Call this whenever the user asks to sign in, log in, authenticate, connect, manage connections or tenants, switch tenants, or says things like 'lokka auth', 'lokka sign in', 'lokka connection'. Also call it when a Lokka query fails because the user is not signed in — in that case pass 'pendingRequest' so the request resumes automatically after sign-in. The UI lets the user sign into one or more Microsoft tenants (as a user or with a service principal), shows the currently active tenant, and switches between connections.
open-lokka-guardrailsOpen the Lokka Guardrails UI for the user. Call this whenever the user says 'lokka guardrails', 'lokka settings', wants to control/limit model tool calls, change which HTTP methods or APIs are allowed, restrict access to specific groups/users/sites, or when a model request was just blocked by a guardrail and the user needs to adjust it. After a block, the app opens to the relevant scope, explains every contributing rule, and offers focused user-controlled fixes. Guardrails can only be changed by the user here — never by the AI. Direct user runs from Graph Explorer are not blocked by guardrails.
open-lokka-helpOpen the Lokka help tour UI for the user. Call this whenever the user says 'lokka help', asks what Lokka can do, how to use Lokka, what tools are available, or wants an overview/tour of Lokka's features. The UI is a visual walkthrough of Graph Explorer, Lokka Settings (connections and guardrails), Connections, Permissions, and chat usage, with one-click launchers and sample prompts.
open-lokka-permissionsOpen the Lokka permissions manager UI for the user. Call this whenever the user asks about Lokka's Microsoft Graph permissions, wants to grant/consent to additional permissions, or says things like 'lokka permissions', 'consent to permissions', 'add graph permissions' — and CALL IT WITH the 'scopes' argument when a Graph call fails with 403 insufficient privileges and you know which permission is missing (e.g. scopes: ['Mail.Read']): the UI opens with those permissions pre-selected so the user only has to approve. The UI shows the currently consented permissions and lets the user search the Graph permission catalog and consent to new ones.
open-lokka-settingsOpen the Lokka settings UI for the user. Call this whenever the user asks for Lokka settings, wants a single place to manage connections or guardrails, or says things like 'lokka settings'. The UI combines the connections manager and guardrails settings; permissions stay in the dedicated Permissions app and inside connection editing.
set-access-tokenSet or update the access token for Microsoft Graph authentication. Use this when the MCP Client has obtained a fresh token through interactive authentication.
switch-lokka-connectionSwitch Lokka's active tenant connection. Use whenever the user asks to switch to a different tenant, account or connection (e.g. 'switch to my dev tenant', 'use the contoso tenant'). Pass any identifying fragment — tenant name, domain, tenant id, username or connection id; it is fuzzy-matched against the signed-in connections. IMPORTANT: after a successful switch, results from earlier in the conversation are from the previous tenant — re-run queries instead of reusing them. If the requested tenant is not in the list, open the connections app (open-lokka-connections) so the user can sign into it.
BEFORE YOU INSTALL
31 tools when we connected. The documentation describes only four; the other 27 are undocumented, and nothing suggests a flag gates them. Lokka-Microsoft is both the server name and the generic Graph/Azure call tool that covers most tasks.
npx on PATH
All 5 documented setups run the server on your machine.
CONTEXT COST
Rated by the size of the 31 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @merill/lokka{
"mcpServers": {
"Lokka-Microsoft": {
"command": "npx",
"args": [
"-y",
"@merill/lokka"
]
}
}
}{
"servers": {
"Lokka-Microsoft": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@merill/lokka"
]
}
}
}{
"servers": {
"Lokka-Microsoft": {
"type": "stdio",
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@merill/lokka"
]
}
}
}{
"mcpServers": {
"Lokka-Microsoft": {
"command": "npx",
"args": [
"-y",
"@merill/lokka"
],
"env": {
"TENANT_ID": "<YOUR_TENANT_ID>",
"CLIENT_ID": "<YOUR_CLIENT_ID>",
"CERTIFICATE_PATH": "<YOUR_CERTIFICATE_PATH>",
"CERTIFICATE_PASSWORD": "<YOUR_CERTIFICATE_PASSWORD>",
"USE_CERTIFICATE": "true"
}
}
}
}{
"mcpServers": {
"Lokka-Microsoft": {
"command": "npx",
"args": [
"-y",
"@merill/lokka"
],
"env": {
"USE_CLIENT_TOKEN": "true"
}
}
}
}MCP servers
softeria
JustStas
Aanerud
elyxlz