Mcp Power Automate
Create and change Microsoft Power Automate flows from an MCP client with browser login, locked targets, review diffs, and rollback.
Overview
io.github.kaael1/mcp-power-automate is an MCP server for the Build phase that manages Power Automate flows locally with browser auth, target locking, review diffs, and rollback.
What is this MCP server?
- Local MCP server for Power Automate with stdio npm package @kaael1/mcp-power-automate v0.4.1
- Browser-backed authentication for Microsoft sign-in flows
- Target locking to avoid editing the wrong flow or environment
- Review diff before apply plus rollback for safer agent edits
- Registry version 0.4.1
- npm identifier @kaael1/mcp-power-automate
- stdio transport local MCP server
Community signal: 18 GitHub stars.
What problem does it solve?
Editing Power Automate flows from an agent is risky without Microsoft login, clear targets, and a way to preview or undo changes.
Who is it for?
Solo builders on Microsoft 365 who want agent-assisted flow changes with guardrails like target locking and rollback.
Skip if: Teams on AWS-only or Zapier-only stacks with no Power Automate tenant, or builders who refuse browser-based Microsoft auth.
What do I get? / Deliverables
After you add the MCP server, agents can propose flow updates with diff review and rollback instead of blind edits in the cloud designer alone.
- Agent-accessible Power Automate flow operations
- Review diff workflow before applying changes
- Rollback path when an automated edit is incorrect
Recommended MCP Servers
Journey fit
Power Automate wiring is a Build integration task when solo builders connect Microsoft 365 automation to products they ship. Integrations is the shelf because the server automates cloud flow authoring, not generic frontend UI or error monitoring.
How it compares
Microsoft Power Automate MCP bridge with safety rails, not a generic HTTP API wrapper or CRM-only integration.
Common Questions / FAQ
Who is mcp-power-automate for?
Builders using Power Automate who want Claude Code, Cursor, or similar agents to modify flows with review and rollback support.
When should I use mcp-power-automate?
Use it during Build when you integrate or refactor Power Automate flows and need locked targets plus diff review before applying agent suggestions.
How do I add mcp-power-automate to my agent?
Install @kaael1/mcp-power-automate from npm, complete browser-backed Microsoft authentication as the server requires, then register the stdio MCP entry in your client config.