Power Automate MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 78 installs a week from npm. Last commit 14 Sep 2026.
Inspect, operate, and author Microsoft Power Automate cloud flows from an agent context.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
ENV TOKEN_CACHE_PATH=/data/token.json
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add power-automate-mcp-server -e 'AZURE_CLIENT_ID=<AZURE_CLIENT_ID>' -e 'AZURE_TENANT_ID=<AZURE_TENANT_ID>' -- npx -y power-automate-mcp-server{
"mcpServers": {
"power-automate-mcp-server": {
"command": "npx",
"args": [
"-y",
"power-automate-mcp-server"
],
"env": {
"AZURE_CLIENT_ID": "<AZURE_CLIENT_ID>",
"AZURE_TENANT_ID": "<AZURE_TENANT_ID>"
}
}
}
}[mcp_servers.power-automate-mcp-server]
command = "npx"
args = ["-y", "power-automate-mcp-server"]
env = { AZURE_CLIENT_ID = "<AZURE_CLIENT_ID>", AZURE_TENANT_ID = "<AZURE_TENANT_ID>" }{
"mcpServers": {
"power-automate-mcp-server": {
"command": "npx",
"args": [
"-y",
"power-automate-mcp-server"
],
"env": {
"AZURE_CLIENT_ID": "<AZURE_CLIENT_ID>",
"AZURE_TENANT_ID": "<AZURE_TENANT_ID>"
}
}
}
}{
"servers": {
"power-automate-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"power-automate-mcp-server"
],
"env": {
"AZURE_CLIENT_ID": "<AZURE_CLIENT_ID>",
"AZURE_TENANT_ID": "<AZURE_TENANT_ID>"
}
}
}
}Put your own values in place of
<AZURE_CLIENT_ID> (Application (client) ID of your Entra app registration (multi-tenant public client)), <AZURE_TENANT_ID> (Tenant GUID. Required for the Flow audience ('common' fails with AADSTS50059)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
FLOW_SCOPES (Comma-separated OAuth scopes (e.g. .../Flows.Read.All,.../Flows.Manage.All)), AZURE_AUTH_MODE (interactive (device-code, default) or clientCredentials (app-only)), AZURE_CLIENT_SECRET (Client secret — only for clientCredentials mode), ENABLE_WRITE_OPS (Set to 'true' to enable mutating tools (default read-only)), DEFAULT_ENVIRONMENT (Environment id used when a tool omits 'environment').
Alternatives to Power Automate MCP Server
same job, measured the same wayInspect, author, validate, and run high-content microscopy workflows.
Debug, build, and manage Power Automate cloud flows with AI agents
Python MCP server for AWS CLI inspection and operations
Convert, validate, and inspect AI agent memories across formats
Place and inspect orders on your own exchange accounts from an MCP-connected agent.
Inspect Kairon VMs, network policy and VM-edge flows from an agent. Read-only by default.
Generate, inspect, and manage Flowstep UI designs directly from your AI assistant.
Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.
Power Automate MCP Server — questions
Answers built from our own checks of this server.