mcpbeat Sign in

Power Automate MCP Server by Flow Studio

answering

Power Automate MCP Server by Flow Studio is answering right now. Last checked 10 min ago. It exposes 29 tools. Last commit 4 Sep 2026.

Debug, build, and manage Power Automate cloud flows with AI agents

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
29
Tools
read from the server
366 ms
Response time
average over 24h
33
Stars
last commit 4 Sep 2026

What changed 90

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.

16 Sep a tool changed version
15 Sep a tool changed version4 times that day
10 Sep 6 tool descriptions were rewritten add_live_flow_to_solution, get_live_flow_run_action_outputs, set_live_flow_state and 3 more
10 Sep 5 tools disappeared get_live_flow_http_schema, get_live_flow_trigger_url, get_store_flow_errors and 2 more
10 Sep a tool changed version
7 Sep a tool changed version3 times that day
7 Sep 2 tools changed the parameters they ask for list_live_environments, list_live_flows
7 Sep 2 tool descriptions were rewritten list_live_environments, list_live_flows
6 Sep a tool changed version
5 Sep 2 tool descriptions were rewritten get_live_flow_run_action_outputs, get_live_flow_runs
and 68 more, back to 12 August 2026

Power Automate MCP Server by Flow Studio missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add flowstudio-mcp --transport http https://mcp.flowstudio.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "flowstudio-mcp": {
      "url": "https://mcp.flowstudio.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.flowstudio-mcp]
url = "https://mcp.flowstudio.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "flowstudio-mcp": {
      "url": "https://mcp.flowstudio.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "flowstudio-mcp": {
      "url": "https://mcp.flowstudio.app/mcp"
    }
  }
}

Available tools 29

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

live
add_live_flow_to_solution
Move a flow into a solution. Refuses if the flow is already in one. solutionId is optional — omit for the default solution.
get_live_dynamic_options
Resolve live dynamic dropdown/list options for a connector operation parameter. Use this when describe_live_connector returns a dynamic parameter with nextTool=get_live_dynamic_options. Works with x-ms-dynamic-list and x-ms-dynamic-values metadata, for example Teams team/channel IDs, SharePoint site/list IDs, or other connector-specific selectable values.
get_live_dynamic_properties
Resolve live dynamic schema/properties for a connector operation parameter. Use this when describe_live_connector returns a dynamicProperties entry with nextTool=get_live_dynamic_properties. Works with x-ms-dynamic-properties and x-ms-dynamic-schema metadata, for example SharePoint item fields after resolving site/list/view parameters.
get_live_flow
Fetch the full native Power Automate flow JSON from the PA API, including the complete flow definition (triggers, actions, parameters, outputs). Returns the raw properties object exactly as the PA API returns it. Use this to inspect the full definition before calling update_live_flow with a modified definition.
get_live_flow_run_action_outputs
Read the recorded inputs and outputs of actions in one flow run. Without actionName: the top-level actions (optionally filtered by name). With actionName: every execution of that action across foreach iterations, each with repetitionIndexes, status, error, and resolved inputs/outputs. Use iterationIndex to pin one iteration; omit it for all. TRIGGER PAYLOADS: set trigger=true with a runName to get that run's trigger inputs and outputs. No Compose workaround is needed. TRIGGER CHECKS: pass checkId (from get_live_flow_runs -> triggerChecks.recent[].checkId) to read a trigger evaluation that never became a run — that is how you see WHY a trigger is failing. Do not supply runName with a checkId.
get_live_flow_run_error
Fetch error details for a specific flow run from the live Power Automate API. Lists every failed action with its error code and message to help diagnose what went wrong.
get_live_flow_runs
Fetch run history for a flow directly from Power Automate. Returns { runs, runCount, triggerChecks }: each run has name, status, startTime, endTime, trigger name/code, and any top-level error. IMPORTANT — no runs does NOT mean the flow is healthy. A trigger that fires and evaluates to nothing, or fails to evaluate, records a TRIGGER CHECK and never becomes a run. When there are no runs (or when includeTriggerChecks is set) this tool also reports the trigger check history, so "nothing ran" can be told apart from "the trigger has been failing". Read triggerChecks.byStatus before concluding a flow is fine.
list_live_connections
List Power Platform connections in an environment directly from Power Automate. Returns id, displayName, connectorName, environment, createdBy (full object), authenticatedUser, statuses, overallStatus, createdTime, expirationTime, and connectionParameters for each connection. Pass search=<term> to narrow the list and receive a paste-ready connectionReferenceTemplate plus action-side hostTemplate per connection — drop these into update_live_flow's connectionReferences and inputs.host without further edits.
list_live_environments
List all Power Platform environments you belong to, directly from Power Automate. Returns id, displayName, sku, location, and state for each environment. mode=all (default) and mode=member: every environment you are a member of. mode=admin: only those you administer; errors rather than guessing if admin access cannot be determined. isAdmin means you hold the ListAnyFlow permission there — the capability list_live_flows mode=admin needs. It is null, never false, when the platform did not tell us. isMember is true for every environment returned.
list_live_flows
List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows you own plus flows shared with you (personal + team), with full definitions. mode=admin: all flows in the environment (requires an admin account). mode=admin with includeDeleted=true also returns soft-deleted flows (state=Deleted) — the only way to find a deleted flow. If search is provided, results are filtered to flows whose displayName contains the search text. For large environments pagination is time-bounded — if nextLink is returned, pass it as continuationUrl to retrieve the next batch.
set_live_flow_state
Start or stop the flow you name. Reads the current state first and only calls Power Automate if a change is actually needed.
update_live_flow
Update or create a flow. Use `dryRun: true` to preview any change without writing. Omit flowName to create: definition and displayName are required. Give flowName to update: displayName and/or definition and/or connectionReferences. SURGICAL EDIT: pass `operations` — an ordered list of set/add/remove/merge ops on array-of-keys paths — to change one action or parameter without resending the whole definition. Provide EITHER operations OR definition; connectionReferences may accompany either and lands in the same save. WHOLE definition: call get_live_flow, mutate properties.definition, pass it here. RENAME: pass displayName alone. Power Automate rejects a PATCH carrying no flow content, so this re-saves the unchanged definition — the maker portal does the same. definition.description is required, and must be brief — we append " #flowstudio-mcp" to it.
store
get_store_flow
[Requires Pro+ plan] Get full details for a single Power Automate flow from the Power Clarity cache. Includes trigger URL, owners, state, run statistics, and governance metadata. Data is from the stored snapshot — not live from the Power Automate API.
get_store_flow_runs
[Requires Pro+ plan] Get cached run history for a flow from the Power Clarity store. Defaults to the last 7 days. Returns startTime, endTime, status, duration (seconds), failedActions, and remediation hint per run. Data is from the stored snapshot — not live from the Power Automate API.
get_store_flow_summary
[Requires Pro+ plan] Get aggregated run statistics for a flow from the Power Clarity cache: total runs, success count, failure count, success rate, fail rate, and average/max duration over a time window. Data is from the stored snapshot — not live from the Power Automate API.
get_store_maker
[Requires Pro+ plan] Get details for a single maker from the Power Clarity cache by their key (usually the AAD object ID). Includes flow/app counts and whether the account has been deleted.
list_store_connections
[Requires Pro+ plan] List all Power Platform connections from the Power Clarity cache.
list_store_environments
[Requires Pro+ plan] List all Power Platform environments from the Power Clarity cache.
list_store_flows
[Requires Pro+ plan] List Power Automate flows from the Power Clarity cache. Optionally filter by governance flags (monitor, notification rules). Returns key fields including trigger URL, state, and run failure rate. Data is from the stored snapshot — not live from the Power Automate API.
list_store_makers
[Requires Pro+ plan] List all makers (citizen developers / AAD users) from the Power Clarity cache.
list_store_power_apps
[Requires Pro+ plan] List all Power Apps canvas apps from the Power Clarity cache.
update_store_flow
[Requires Pro+ plan] Update governance/metadata fields on a flow record in the Power Clarity store (description, business impact, owner team, tags, monitor flag, notification settings, etc.). Only fields provided are updated (merge semantics). Writes to the cache — does not call the Power Automate API.
cancel
cancel_live_flow_run
Cancel a currently running Power Automate flow run via the live PA API. Use after get_live_flow_runs to obtain the run name. Only runs with status "Running" can be cancelled.
describe
describe_live_connector
Describe a live Power Platform connector/API and its operations. Aligned with Canvas MCP describe_api. Use mode=summary (default) to get a compact operation catalog. Use operationId to describe one operation, including inputs, outputs, dynamic parameter metadata, nextTool hints to call get_live_dynamic_options, and an authored hint + canonical example shape (when one exists) to copy into update_live_flow. Use search without connectorName/apiName to search operations across connectors and get connection-aware suggestions. Use mode=full only when raw OpenAPI connector metadata is required.
report
report_bug
Report a Flow Studio MCP bug or missing capability, append text evidence, or check your reports. Free and available even after quota is reached. Do not include passwords, access tokens, secrets, or full flow definitions unless necessary.
resubmit
resubmit_live_flow_run
Resubmit a failed or cancelled Power Automate flow run via the live PA API, re-using the original trigger payload. Discovers the trigger name from the flow definition automatically — no trigger name parameter needed.
skills
list_skills
List all skill bundles — named groups of tools the agent typically uses together for a single user intent (diagnose-connection-references, build-flow, debug-flow, monitor-flow, discover, governance). Returns each skill's description and member tool names. Call this first when you are unsure which tools apply to a request; then call tool_search with query: "skill:<name>" to load the full bundle. Non-billable.
tool
tool_search
Find the right tool instead of guessing its name. Returns full JSON schemas, ready to call. Query forms: (1) "skill:<name>" — a whole bundle; call list_skills for the names; (2) "select:name1,name2" — exact tools; (3) free text like "cancel run" — ranked against name and description. Non-billable.
trigger
trigger_live_flow
Run a flow on demand — the same as the maker portal's "Run flow" button. Works with Request triggers (HTTP request, manual Button, PowerApps) and with scheduled RECURRENCE flows, which run immediately; a scheduled flow takes no inputs, so passing `body` to one is refused. Pass trigger inputs as `body`. Automated connector triggers only fire from their source event.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

describe_canvas_app_controls
removed 27 Aug 2026
describe_canvas_control_type
removed 27 Aug 2026
diff_canvas_app
removed 27 Aug 2026
discard_canvas_app_session
removed 27 Aug 2026
get_canvas_app
removed 27 Aug 2026
get_canvas_app_data_sources
removed 27 Aug 2026
get_canvas_app_files
removed 27 Aug 2026
list_canvas_apps
removed 27 Aug 2026
list_canvas_app_versions
removed 27 Aug 2026
publish_canvas_app
removed 27 Aug 2026
update_canvas_app
removed 27 Aug 2026
update_canvas_app_files
removed 27 Aug 2026
get_live_flow_http_schema
removed 10 Sep 2026
get_live_flow_trigger_url
removed 10 Sep 2026
get_store_flow_errors
removed 10 Sep 2026
get_store_flow_trigger_url
removed 10 Sep 2026
set_store_flow_state
removed 10 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://mcp.flowstudio.app/mcp streamable-http answering 320 ms 10 min ago

Alternatives to Power Automate MCP Server by Flow Studio

same job, measured the same way
Browser Agent
by runbook-ai

MCP server for browser automation with AI agent

62 installs/wk local only
Safari DevTools MCP
by hayodev

MCP server for Safari DevTools — browser debugging and automation for AI coding agents

55 installs/wk local only
SideButton MCP Server
by sidebutton

Open-source MCP server with browser automation and knowledge packs for AI agents

111 installs/wk local only
I
Prefect MCP Server
by prefecthq

MCP server for Prefect. Monitor and debug workflows, deployments, and automations.

2 259 installs/wk local only
ManageLM
by managelm

AI Linux & Windows server management with Claude MCP and fully private agents using local AI

answering
R
Syncline MCP Server
by syncline

AI-powered meeting scheduling with intelligent auto-scheduling for Claude and AI agents.

218 installs/wk local only
FiveM MCP
by ziyacivan

Build, run and live-test FiveM servers with AI agents: RCON, DevCon, window control, mcpb bridge.

67 installs/wk local only
I
WireMock Cloud
by wiremock

Build, validate, and manage API simulations in WireMock Cloud from MCP-compatible AI agents.

answering

Power Automate MCP Server by Flow Studio — questions

Answers built from our own checks of this server.

What can Power Automate MCP Server by Flow Studio do?
It exposes 29 tools, read directly from the server on our last check. Among them: add_live_flow_to_solution, cancel_live_flow_run, describe_live_connector, get_live_dynamic_options, get_live_dynamic_properties, get_live_flow and 23 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Power Automate MCP Server by Flow Studio mostly used for?
Its tools cluster around live and store. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Power Automate MCP Server by Flow Studio working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 366 ms. The bar chart above shows every period we have measured.
Did Power Automate MCP Server by Flow Studio ever remove tools?
Yes. describe_canvas_app_controls, describe_canvas_control_type, diff_canvas_app, discard_canvas_app_session and 13 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Power Automate MCP Server by Flow Studio?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Power Automate MCP Server by Flow Studio need an API key?
No. Power Automate MCP Server by Flow Studio completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 29 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Power Automate MCP Server by Flow Studio?
It answers our handshake in 366 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Power Automate MCP Server by Flow Studio open source?
Yes — it is published under the MIT licence, written in JavaScript, 33 stars on GitHub and 6 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.