FastMCP FastMCP
Sign In
L

Lokka (Microsoft Graph)

Provides a bridge between Microsoft Graph API and natural language interaction, enabling conversatio...

3 views
0 installs
Updated Dec 25, 2025
Not audited
Cloud Platforms Automation
Provides a bridge between Microsoft Graph API and natural language interaction, enabling conversational management of Microsoft 365 tenants without complex API calls.

  1. Click the "Install Now" button and open the FastMCP connection interface — you will paste each ENV value into the FastMCP fields for the Lokka MCP server configuration. (lokka.dev)

  2. If you want the simplest, out‑of‑the‑box experience (Interactive auth with the default Lokka app) — no ENV variables are required. Just install Lokka and sign in when prompted. (lokka.dev)

  3. To use a custom Interactive Microsoft Entra (Azure AD) app (you must supply TENANT_ID and CLIENT_ID):

    1. Open the Microsoft Entra (Azure AD) portal → App registrations → New registration. Enter a name and Register. (learn.microsoft.com)
    2. In the app’s Redirect URI section choose “Public client / native (mobile & desktop)” and enter http://localhost (or the redirect URI you plan to use). (lokka.dev)
    3. Add the delegated Microsoft Graph permissions you need (start with User.Read.All to list users). Add permissions and Grant admin consent. (lokka.dev)
    4. Copy the Application (client) ID and Directory (tenant) ID from the app Overview — these become CLIENT_ID and TENANT_ID. Paste them into FastMCP fields named CLIENT_ID and TENANT_ID, and set USE_INTERACTIVE = true in FastMCP. (lokka.dev)

  4. To use App‑Only auth with a client secret (server/service credentials):

    1. Register a new app in Entra ID (App registrations → New registration) if you haven’t already. (learn.microsoft.com)
    2. In the app, go to API permissions → Add a permission → Microsoft Graph → Application permissions. Add the application permissions your agent requires and Grant admin consent. (lokka.dev)
    3. Go to Certificates & secrets → Client secrets → New client secret. Create it and immediately copy the secret value (this is CLIENT_SECRET). Paste CLIENT_SECRET, plus CLIENT_ID and TENANT_ID, into the FastMCP fields. (lokka.dev)

  5. To use App‑Only auth with a certificate (recommended for app‑only):

    1. Create or obtain a client certificate (PFX) for your app. In the Entra app, upload the public certificate under Certificates. (lokka.dev)
    2. Convert PFX → PEM on the machine that will run Lokka (so Lokka can read the PEM file) using the command shown in the docs:
      openssl pkcs12 -in /path/to/cert.pfx -out /path/to/cert.pem -nodes -clcerts
      Use the resulting PEM file path as CERTIFICATE_PATH. (lokka.dev)
    3. In FastMCP set TENANT_ID and CLIENT_ID, set CERTIFICATE_PATH to the PEM file path, set USE_CERTIFICATE = true, and fill CERTIFICATE_PASSWORD if your PEM is encrypted. (lokka.dev)

  6. To use client‑provided tokens (token auth / development mode):

    1. In FastMCP set USE_CLIENT_TOKEN = true for the Lokka connection. (lokka.dev)
    2. Start the Lokka MCP server and then provide a valid Microsoft Graph access token using the Lokka tool set-access-token (or paste a short‑lived token into the FastMCP ACCESS_TOKEN field if supported). Verify with get-auth-status. Tokens can be obtained via Azure CLI, Graph Explorer, or Graph PowerShell (examples in the docs). (lokka.dev)

  7. Optional/other ENV values to set in FastMCP as needed:

    • REDIRECT_URI — if you changed it when registering your app, paste the exact redirect URI. (Lokka defaults / examples reference http://localhost variants.) (lokka.dev)
    • USE_GRAPH_BETA — set to "false" in FastMCP if you want all Graph calls to use v1.0 instead of beta. (github.com)

  8. After you paste the values into the FastMCP connection interface:

    1. Save the connection.
    2. Restart / re‑connect the MCP client (Claude Desktop, VS Code, etc.) so the new ENV values are used. Test by performing a simple query (e.g., "Get all users") or by running get-auth-status / set-access-token as appropriate. (lokka.dev)

  9. Security reminders (do this before pasting secrets/certs into FastMCP):

    1. Treat CLIENT_SECRET and certificate private keys as sensitive — store them securely and rotate them periodically. Copy the client secret value immediately when you create it (it is shown only once in Entra). (learn.microsoft.com)

If you want, tell me which authentication method you plan to use (Interactive default, Interactive custom, App‑Only secret, App‑Only certificate, or Token mode) and I’ll produce the exact FastMCP field values and a minimal checklist you can paste directly into the FastMCP connection form.

Quick Start

View on GitHub Visit Website

More for Cloud Platforms

View All →

More for Automation

View All →

Report Issue

Thank you! Your issue report has been submitted successfully.