Developer · Local MCP server
Power Automate MCP Server
Inspect, operate, and author Microsoft Power Automate cloud flows from an agent context.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sapientsai/power-automate-mcp-server- Version
- 0.2.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-26
- Updated
- 2026-06-26
- Publisher
- sapientsai (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sapientsai) · how
- Repository
- github.com/sapientsai/power-automate-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | power-automate-mcp-server | 0.2.4 | stdio |
How to connect Power Automate MCP Server
Power Automate MCP Server runs locally from a Node.js package published to the npm registry: power-automate-mcp-server version 0.2.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y power-automate-mcp-server@0.2.4. It reads these environment variables: AZURE_CLIENT_ID (required), AZURE_TENANT_ID (required), FLOW_SCOPES, AZURE_AUTH_MODE, AZURE_CLIENT_SECRET (secret), ENABLE_WRITE_OPS and DEFAULT_ENVIRONMENT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"power-automate-mcp-server": {
"command": "npx",
"args": [
"-y",
"power-automate-mcp-server@0.2.4"
],
"env": {
"AZURE_CLIENT_ID": "<value>",
"AZURE_TENANT_ID": "<value>",
"FLOW_SCOPES": "<value>",
"AZURE_AUTH_MODE": "<value>",
"AZURE_CLIENT_SECRET": "<secret>",
"ENABLE_WRITE_OPS": "<value>",
"DEFAULT_ENVIRONMENT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from sapientsai (GitHub)
| Server | Runs |
|---|---|
| Dokploy MCP ServerDokploy MCP server: manage apps, Docker Compose, databases, domains, backups, and servers. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| PostgreSQL MCP ServerEnterprise PostgreSQL MCP server with 63 tools, 10 resources, 10 prompts for AI-native operations. | Local · stdio |
| PostgreSQL MCP ServerPostgreSQL MCP server - query, schema introspection, explain, and health checks for AI assistants. | Local · stdio |
| PostifySchedule, publish, and analyze social posts across 11 platforms from any MCP client. | Remote · HTTPLive check: sign-in required |
| Pour PicksSearch the Pour Picks bourbon & whiskey database: 4,700+ bottles with tasting profiles and prices. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Power Automate MCP Server by Flow StudioDebug, build, and manage Power Automate cloud flows with AI agents. | Remote · HTTPLive check: ✓ handshake |
| Power Portals ProComponent API, code samples and Dataverse metadata for building Power Portals Pro portals. | Local · stdio |
| Powershell MCPHeadless Windows ops over MCP: hidden PowerShell plus in-process SSH, WinRM and SFTP. | Local · stdio |
| Pptmasterdeck MCPA paid remote MCP for ppt-master, built to return verdicts, receipts, usage logs, and audit-ready JS. | Remote · HTTPLive check: ✗ no handshake |