MCP Tools Reference
Overview
Flow Studio MCP provides 25+ tools organized into two tiers. Live tools are available to all MCP subscribers and call the Power Automate API directly — data is always current. Store tools are available to Teams subscribers and read from the Flow Studio data store — the same Azure Storage backend that powers Flow Studio for Teams monitoring, enriched with governance metadata and run statistics.
Your agent can discover all available tools automatically by calling tools/list at the start of a session. This returns the authoritative schema for every tool — parameter names, types, and required flags.
Live Tools — All Plans
These tools call the Power Automate API directly. Data is always real-time.
Environment and Connection Discovery
| Tool | What it does |
|---|---|
| list_live_environments | List all Power Platform environments visible to your account. Returns environment IDs, display names, regions, and SKUs. Use the id value as environmentName in all other tools. |
| list_live_connections | List all connections in an environment. Returns connection IDs, connector names, status, and creator info. Use the id value as connectionName in connection references. |
Flow Management
| Tool | What it does |
|---|---|
| list_live_flows | List flows in an environment. Returns flow IDs, display names, state, trigger type, and timestamps. The response includes a flows array — access via result["flows"]. |
| get_live_flow | Fetch the complete flow definition — triggers, actions, parameters, and connection references. This is the full JSON you would see in the Power Automate code view. |
| update_live_flow | Create a new flow or update an existing flow definition. Pass the full definition and connection references. Omit flowName to create; include it to update. |
| set_live_flow_state | Start or stop a flow. Use this instead of update_live_flow for state changes. |
| add_live_flow_to_solution | Migrate a non-solution flow into a solution for ALM. |
Run Inspection and Debugging
| Tool | What it does |
|---|---|
| get_live_flow_runs | List recent run history with status, timestamps, trigger name, and error summary. Returns newest first. Default: 30 runs; supports higher values with auto-pagination. |
| get_live_flow_run_error | Get structured error details for a failed run. Returns per-action failure breakdown with error codes and messages. The last entry in failedActions is typically the root cause. |
| get_live_flow_run_action_outputs | Inspect the inputs and outputs of any action in a run. Omit actionName to get all actions; provide it to get one. Supports loop iteration inspection. |
Run Execution
| Tool | What it does |
|---|---|
| trigger_live_flow | POST to an HTTP-triggered flow’s callback URL. Only works for Request (HTTP) triggers. AAD authentication is handled automatically. |
| resubmit_live_flow_run | Re-run a failed or cancelled run using its original trigger payload. |
| cancel_live_flow_run | Cancel a currently running flow execution. Do not cancel runs waiting for an adaptive card response — that status is normal. |
HTTP Trigger Tools
| Tool | What it does |
|---|---|
| get_live_flow_http_schema | Inspect the JSON body schema and response schemas of an HTTP-triggered flow. Returns the expected request body, headers, and defined response schemas. |
| get_live_flow_trigger_url | Get the signed callback URL for an HTTP-triggered flow. |
|
Note: Flow Studio MCP does not include a delete flow tool. Deleting flows must be done through the Power Automate portal. This is intentional — delete operations are irreversible and should require manual confirmation. |
Store Tools — Teams Plans
These tools read from the Flow Studio data store — the same Azure Storage backend used by Flow Studio for Teams. This includes governance metadata, run statistics, maker information, and flow run history retained beyond Microsoft’s 28-day limit.
Flow Governance
| Tool | What it does |
|---|---|
| list_store_flows | Search flows with governance flags, run failure rates, and owner metadata. |
| get_store_flow | Full details for a single flow including run stats, governance fields, complexity, and connector list. |
| get_store_flow_summary | Aggregated run statistics: total runs, fail rate, average/max duration, and remediation hints. |
| get_store_flow_runs | Run history for the last N days with duration and remediation hints. |
| get_store_flow_errors | Failed-only runs with failed action names and remediation hints. |
| get_store_flow_trigger_url | Trigger URL from the data store (instant, no PA API call needed). |
| update_store_flow | Update governance metadata: description, tags, monitor flag, notification rules, business impact. |
| set_store_flow_state | Start/stop a flow via the PA API and sync the result back to the data store. |
Tenant Discovery
| Tool | What it does |
|---|---|
| list_store_environments | List all environments from the data store. |
| list_store_makers | List all makers (citizen developers) with their flow/app counts. |
| get_store_maker | Get a specific maker’s flow and app counts and account status. |
| list_store_power_apps | List all Power Apps canvas apps from the data store. |
| list_store_connections | List all Power Platform connections from the data store. |
Which tool should I use?
When in doubt, use live tools — they work for all subscription tiers and return real-time data.
| Task | Recommended tool | Why |
|---|---|---|
| List my flows | list_live_flows | Always current from the PA API |
| Read a flow definition | get_live_flow | Always fetched live from the PA API |
| Debug a failure | get_live_flow_runs → get_live_flow_run_error | Live run data with per-action errors |
| Check overall flow health | get_store_flow_summary | Aggregated stats over time (Teams) |
| Find who owns a flow | list_store_flows | Owner metadata from data store (Teams) |
| Start or stop a flow | set_live_flow_state | Direct API call, not update_live_flow |
Tool discovery
Your agent can discover all available tools automatically at the start of each session by calling tools/list. This returns the complete schema for every tool — parameter names, types, and required flags. The tools/list call is free and does not count against your plan limits.
If any documentation on this page differs from what tools/list returns, trust tools/list — it is always the authoritative source.
API usage and limits
Each tool call (except tools/list) counts as one MCP call against your plan. If you hit your plan limit, tool calls return MCP error -32000: Plan limit reached. Check your usage on your dashboard.
Related guides
- Getting Started with Flow Studio MCP — Set up your connection
- Debug Power Automate Flows with MCP — Step-by-step debugging workflow
- Build Power Automate Flows with MCP — Create flows from scratch