io.github.kaael1/mcp-power-automate

Name: io.github.kaael1/mcp-power-automate
Rating: 60 (1 reviews)
Author: io.github.kaael1

MCPcommunity

v0.4.1io.github.kaael1UnknownUpdated 3mo agonpm GitHub

Local MCP for Power Automate with browser-backed auth, target locking, review diff, and rollback.

Local MCP server, Chromium extension, and optional Codex skill for operating Microsoft Power Automate flows from a local browser-backed session. No Microsoft Entra ID app registration, admin consent, or custom enterprise app setup is required. This MCP uses your existing logged-in browser session instead, which is often much easier to adopt inside locked-down companies. Built for MCP users who…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

3mo agoLast update

Package

Authorio.github.kaael1

LicenseUnknown

Version0.4.1

Sourcemcp-registry

npm@kaael1/mcp-power-automate

GitHubkaael1/mcp-power-automate

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface22 tools · none privileged

Security scan✓ Cleanv0.4.1 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp