Power Automate MCP Server vs MCP Power Automate

In-depth architectural comparison of the Power Automate MCP Server and MCP Power Automate MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

P

Choose Power Automate MCP Server when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Power Automate MCP Server Details

Choose MCP Power Automate when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore MCP Power Automate Details

Feature & Specification Comparison

Specification	P Power Automate MCP Server Developer Tools	MCP Power Automate Developer Tools
Summary	Inspect, operate, and author Microsoft Power Automate cloud flows from an agent context.	Local MCP for Power Automate flows with browser-backed auth, extension, and Codex skill.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "power-automate-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "power-automate-mcp-server"
      ]
    }
  }
}

{
  "mcpServers": {
    "mcp-power-automate": {
      "command": "npx",
      "args": [
        "-y",
        "@kaael1/mcp-power-automate"
      ]
    }
  }
}

Related MCP Server Comparisons