Connect Power Automate MCP Server by Flow Studio and your agent gets 29 tools, among them add_live_flow_to_solution, cancel_live_flow_run, describe_live_connector. It answers at https://mcp.flowstudio.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Debug, build, and manage Power Automate cloud flows with AI agents
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: environmentName, flowName, solutionId |
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. Inputs: environmentName, flowName, runName |
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, dyna Inputs: environmentName, connectorName, apiName, mode, operationId, type |
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 m Inputs: environmentName, connectorName, apiName, operationId, parameterName, connectionName |
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-dynam Inputs: environmentName, connectorName, apiName, operationId, parameterName, connectionName |
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 ful Inputs: environmentName, flowName |
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 Inputs: environmentName, flowName, runName, trigger, checkId, actionName |
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. Inputs: environmentName, flowName, runName, top |
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 h Inputs: environmentName, flowName, top, includeTriggerChecks |
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 Au Inputs: environmentName, flowName |
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 s Inputs: environmentName, flowName, startTime, endTime, status, top |
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 — n Inputs: environmentName, flowName, startTime, endTime |
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. Inputs: makerKey |
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 conne Inputs: environmentName, top, search |
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: Inputs: mode, top |
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=admi Inputs: environmentName, mode, includeDeleted, top, search, continuationUrl |
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 mem |
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 Inputs: monitor, rule_notify_onfail, rule_notify_onmissingdays |
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. |
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. Inputs: action, summary, details, ticket, tool_name, category |
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. Inputs: environmentName, flowName, runName |
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. Inputs: environmentName, flowName, state |
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 Inputs: query, max_results |
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 p Inputs: environmentName, flowName, body |
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. SURGICA Inputs: environmentName, flowName, displayName, definition, connectionReferences, operations |
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 semantic Inputs: environmentName, flowName, description, businessImpact, businessJustification, businessValue |
Every block below points at https://mcp.flowstudio.app/mcp. Pick your client and copy.
claude mcp add --transport http power-automate-mcp-server-by-flo https://mcp.flowstudio.app/mcp
{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.flowstudio.app/mcp"]
}
}
}{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"url": "https://mcp.flowstudio.app/mcp"
}
}
}{
"servers": {
"power-automate-mcp-server-by-flo": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp"
}
}
}{
"context_servers": {
"power-automate-mcp-server-by-flo": {
"url": "https://mcp.flowstudio.app/mcp"
}
}
}{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"serverUrl": "https://mcp.flowstudio.app/mcp"
}
}
}{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"url": "https://mcp.flowstudio.app/mcp"
}
}
}name: Power Automate MCP Server by Flow Studio
version: 0.0.1
schema: v1
mcpServers:
- name: Power Automate MCP Server by Flow Studio
type: streamable-http
url: https://mcp.flowstudio.app/mcp{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"httpUrl": "https://mcp.flowstudio.app/mcp"
}
}
}{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp"
}
}
}{
"mcpServers": {
"power-automate-mcp-server-by-flo": {
"url": "https://mcp.flowstudio.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.flowstudio.app%2Fmcp&type=streamable_http&id=power-automate-mcp-server-by-flo&name=Power%20Automate%20MCP%20Server%20by%20Flow%20Studio
It answered our last check on 22 October 2026 in 292 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
29, as returned by the server's own tools/list on 17 September 2026: add_live_flow_to_solution, cancel_live_flow_run, describe_live_connector, get_live_dynamic_options, get_live_dynamic_properties, get_live_flow, get_live_flow_run_action_outputs, get_live_flow_run_error, and 21 more.
It answered our last check on 22 October 2026 in 292 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.flowstudio.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.ninihen1. Endpoint host: mcp.flowstudio.app. ARD identifier: urn:air:io.github.ninihen1:mcp:flowstudio-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.