Lokka MCP server

Read from the package source without running it. The installed server may list more.

• Lokka-Microsoft

  A 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/ten

• add-graph-permission

  Request 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-status

  Check 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-connection

  Internal: add an app-only connection that authenticates with a client certificate (PEM). Used by the Lokka connections app UI.

• lokka-add-sp-connection

  Internal: add a service principal (client credentials) connection to a Microsoft tenant. Used by the Lokka connections app UI.

• lokka-add-user-connection

  Internal: sign into a Microsoft tenant interactively (browser) and add it as a Lokka connection. Used by the Lokka connections app UI.

• lokka-connect-created-app

  Internal: 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-permissions

  Internal: request or remove Microsoft Graph delegated permission scopes for the active connection. Used by the Lokka permissions app UI.

• lokka-create-appwrite action

  Internal: 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-guardrails

  Get 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-config

  Internal: full guardrails config plus the connected tenants and resource presets, for the Guardrails app editor.

• lokka-get-permissions

  Internal: get the Microsoft Graph permissions (scopes/roles) currently granted to Lokka's active connection. Used by the Lokka permissions app UI.

• lokka-grant-app-permissions

  Internal: 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-connections

  List 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-reconnect-connection

  Internal: 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-connectionwrite action

  Internal: remove a Lokka tenant connection. Used by the Lokka connections app UI.

• lokka-remove-guardrails-tenantwrite action

  Internal: remove a tenant's guardrails rule so it reverts to Global only. Used by the Guardrails app.

• lokka-search-directory

  Internal: 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-connection

  Internal: switch Lokka's active tenant connection. Used by the Lokka connections app UI.

• lokka-set-connection-label

  Internal: set a friendly display label for a connection (empty clears it). Used by the Lokka connections app UI.

• lokka-set-guardrails-enabled

  Internal: 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-scope

  Internal: replace the guardrails policy for a scope ('global' or a tenant id). Used by the Guardrails app.

• lokka-update-app-credentialwrite action

  Internal: 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-explorer

  Open 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-connections

  Open 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 si

• open-lokka-guardrails

  Open 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

• open-lokka-help

  Open 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-permissions

  Open 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

• open-lokka-settings

  Open 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-token

  Set 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-connection

  Switch 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 conve

• Code scan8 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

65/100

higher than 20% of 48,273 servers

Tools

31

the typical server has 7

Tools that change things

13%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

563

more than 90% of 11,915 servers with a package

Lokka: common questions

Is Lokka MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Lokka safety report

How do I install Lokka?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Lokka need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Lokka maintained?

The latest release is v2.1.2.

What can I use instead of Lokka?

Servers from other publishers that do the same job: Microsoft 365 MCP Server.

How does Lokka compare with other MCP servers?

safety score 65/100 (higher than 20% of 48,273 servers); tools 31 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.