Lokka

io.github.jozrahqPublished by GitHub account jozrahqv2.1.2Updated Oct 30, 2026

Query and manage Microsoft Graph and Azure Resource Manager APIs from MCP clients.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an assistant query and manage Microsoft Graph and Azure Resource Manager APIs.

What you can do
  • Query and manage Microsoft Graph resources through the assistant
  • Query and manage Azure Resource Manager resources through the assistant
  • Work with Microsoft 365 and Azure data from an MCP client
  • No individual tools are documented in the supplied listing, so exact operations are not specified
When to use it
Worth adding when you want an assistant to work with Microsoft 365 or Azure resources through Graph and Resource Manager APIs from a desktop MCP client, instead of switching to the portals or writing scripts.
Requirements
Runs as a local process over stdio, installed from the npm package @merill/lokka, so Node.js and npm are needed. Desktop MCP client only; no web executable. No authentication method, environment variables or headers are declared in the manifest, so how it obtains Microsoft credentials is not stated.
Before you install
The server is described as able to manage Graph and Azure Resource Manager resources, so actions may change or delete cloud and tenant data. No authentication details are declared, so check how it obtains and stores Microsoft credentials before use. Review which operations it exposes before granting access to a production tenant or subscription.

Installation

In SourceWeft

  1. Open Lokka in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.