Categories › Productivity & Office › Project & task management
Debug, build, and manage Power Automate cloud flows with AI agents
Remote server: your requests and data go to mcp.flowstudio.app. Claude Code: claude mcp add --transport http power-automate-mcp-server-by-flow-studio https://mcp.flowstudio.app/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
tool_search — Find a tool listed here instead of guessing its name, and get its definition. Query forms: (1) "skill:<name>" — a whole bundle; call list_sklist_skills — Skill bundles: groups of the tools listed here that are used together for one task (diagnose-connection-references, build-flow, debug-flow, 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 reacget_task — Get the status and result of a long-running tool call. When a tool replies with a taskId and status "working", the work is still running on list_store_flows — [Requires Pro+ plan] List Power Automate flows from the Power Clarity cache. Optionally filter by governance flags (monitor, notification ruget_store_flow — [Requires Pro+ plan] Get full details for a single Power Automate flow from the Power Clarity cache. Includes trigger URL, owners, state, ruget_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, endTimeget_store_flow_summary — [Requires Pro+ plan] Get aggregated run statistics for a flow from the Power Clarity cache: total runs, success count, failure count, succesupdate_store_flow — [Requires Pro+ plan] Update governance/metadata fields on a flow record in the Power Clarity store (description, business impact, owner teamlist_store_environments — [Requires Pro+ plan] List all Power Platform environments from the Power Clarity cache.list_store_makers — [Requires Pro+ plan] List all makers (citizen developers / AAD users) from the Power Clarity cache.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/applist_store_power_apps — [Requires Pro+ plan] List all Power Apps canvas apps from the Power Clarity cache.list_store_connections — [Requires Pro+ plan] List all Power Platform connections from the Power Clarity cache.get_live_flow_runs — Fetch run history for a flow directly from Power Automate. Returns { runs, runCount, triggerChecks }: each run has name, status, startTime, 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 hget_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). Witrigger_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, PowerAppscancel_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 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 namset_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.get_live_flow — Fetch the full native Power Automate flow JSON from the PA API, including the complete flow definition (triggers, actions, parameters, outpuget_live_flow_versions — List a flow's versions, newest first. A flow in a solution lists every published version. Any other flow lists only versions that ran.diff_live_flow — Compare two versions of a flow. Returns the actions added, removed and changed.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 rlist_live_environments — List all Power Platform environments you belong to, directly from Power Automate. Returns id, displayName, sku, location, and state for eachlist_live_flows — List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (delist_live_connections — List Power Platform connections in an environment directly from Power Automate. Returns id, displayName, connectorName, environment, createddescribe_live_connector — Describe a live Power Platform connector/API and its operations. Use mode=summary (default) to get a compact operation catalog. Use operatioadd_to_solution — Add a flow or a canvas app to a solution. Pass flowName or app. A flow not yet in a solution moves into `solution`, or into the default soluresolve_live_parameters — Resolve a connector action's inputs the way the flow designer does: dropdown options, list and table columns, folder and file pickers — evertest_live_connection — Test a connection, or run one operation on it. Without operationId it runs the connector's own connection test. With operationId it runs thacreate_live_connection — Create a connection, or sign an existing one in again (pass connectionName). Shows a sign-in card where the person signs in; you never sign read_live_table — Read rows from a Dataverse table, SharePoint list, SQL table or Excel table. Read-only. Returns rows, columns and nextLink.grant_flow_studio_access — Shows a sign-in card; the person signs in, or signs in again when expired. Flow Studio keeps the sign-in for later calls.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.