list_live_flowsLABSCO SUMMARY
Your agent stops being blind at the point the flow broke.
A failed run in the portal is a click-through exercise; through here it is a query. The agent reads the failing action's actual inputs, follows the call into the child flow, and can push the corrected definition back — without you acting as the middle-man between it and the browser.
What it is
A hosted MCP endpoint plus five agent skills for Power Automate. The gap it fills is specific: the Graph API returns top-level run status, so an agent can see that a flow failed but not why. This exposes the action-level detail a human gets in the portal — inputs, outputs, error detail, child-flow runs and per-iteration loop data.
What you get
- Live operation — list flows, read definitions as full JSON, check runs, resubmit and cancel, and deploy a fixed definition with
update_live_flow - Action-level visibility — the inputs and outputs of every action, error detail beyond the status code, child flow run details, and loop iteration data the agent can scan all at once
- Five skills, each following the Agent Skills specification:
power-automate-mcpfor connecting and operating,power-automate-debugfor a step-by-step diagnostic process,power-automate-buildfor scaffolding and deploying definitions,power-automate-monitoringfor flow health, failure rates, maker and Power Apps inventory, andpower-automate-governancefor impact classification, orphan detection, connector audits and archive scores - Worked investigations in the repository, including an expression failure traced from parent flow through a child flow into a loop iteration
Requirements
A FlowStudio subscription and an API key, passed as the x-api-key header against the endpoint https://mcp.flowstudio.app/mcp over HTTP transport — there is nothing to install for the server itself. The monitoring and governance skills read a cached daily snapshot rather than live data and need FlowStudio for Teams or MCP Pro+; the first three skills use live API calls. Skills install through the Claude plugin marketplace, $skill-installer in Codex, npx skills add, ClawHub or Smithery, or by copying the folder into wherever your agent discovers skills.
Setup effort
One command plus a key — claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp --header "x-api-key: <YOUR_TOKEN>", then supply credentials
USE CASES
01
Finding out why a flow failed
Read the run, open the failing action's inputs and outputs, and follow the error into the child flow instead of stopping at the status code.
02
Checking a loop with hundreds of iterations
The agent scans every iteration's inputs and outputs at once, rather than you clicking through them one at a time in the portal.
03
Shipping the fix
Edit the definition and deploy it to the live flow from the same session that diagnosed the problem.
04
Deciding whether it is the flow or the data
With the real inputs visible, a bad address or a null field is distinguishable from a logic error in seconds.
05
Surveying flow health across the tenant
Use the monitoring skill's cached snapshot for failure rates, maker inventory and connection counts without opening the admin centre.
06
Auditing what has been left behind
Classify flows by impact, detect orphaned resources and audit connectors at scale, without installing the CoE Starter Kit.
28 tools
Listed in project docs. Your client may show a different list.
list_live_environmentslist_live_connectionsget_live_flowget_live_flow_runsget_live_flow_run_errorget_live_flow_run_action_outputsget_live_flow_http_schemaget_live_flow_trigger_urltrigger_live_flowupdate_live_flowresubmit_live_flow_runcancel_live_flow_runset_live_flow_stateadd_live_flow_to_solutionlist_store_flowsget_store_flowget_store_flow_runsget_store_flow_errorsget_store_flow_summaryget_store_flow_trigger_urllist_store_environmentslist_store_connectionslist_store_makersget_store_makerlist_store_power_appsupdate_store_flowset_store_flow_stateBEFORE YOU INSTALL
What to know first
Tools you get
28 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code
TERMINAL
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp --header "x-api-key: <YOUR_TOKEN>"Hosted endpoint
ENDPOINT URL
https://mcp.flowstudio.app/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Codex
CODEX · TOML
[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"
[mcp_servers.flowstudio.http_headers]
x-api-key = "<YOUR_TOKEN>"VS Code
VS CODE · JSON
{
"servers": {
"flowstudio": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp",
"headers": {
"x-api-key": "<YOUR_TOKEN>"
}
}
}
}
