Power Automate MCP Server by Flow Studio

Official33 toolsLive

by ninihen1 · JavaScript

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

FlowStudio MCP (io.github.ninihen1/flowstudio-mcp)

FlowStudio MCP provides MCP access to Power Automate cloud flows so AI agents can debug, build, and manage them. It addresses a gap where the Graph API only returns top-level run status, limiting agent visibility into action inputs, loop iterations, or nested failures.

🛠️ Key Features

Debug, build, and manage Power Automate cloud flows
Exposes action inputs, loop iterations, and nested failure details beyond top-level run status

🚀 Use Cases

Agent-based troubleshooting for Power Automate flows
Identifying root causes that are visible in the Power Automate portal but not via Graph API alone

⚡ Developer Benefits

More complete runtime visibility for AI agents than Graph API provides
Ability to click through portal-style detail for diagnosing root causes

⚠️ Limitations

The readme excerpt highlights that Graph API exposes only top-level run status; FlowStudio MCP is positioned to go beyond that, but specific coverage breadth is not detailed here

Topics

gemini-cli-extension

Captured live from the server via tools/list.

tool_search

PREFER THIS over guessing tool names when picking from this server. Searches Flow Studio MCP tools by keyword, skill bundle, or explicit selector and returns full JSON schemas for matched tools so they can be called immediately. Call this whenever the user request maps to functionality you are not 100% sure about, OR when you want to load a whole skill bundle (build-flow, debug-flow, monitor-flow, discover, governance) at once. Query forms: (1) "skill:<name>" — fetch the full bundle (use list_skills first to see options); (2) "select:name1,name2" — fetch exact tools by name; (3) free-text keywords like "cancel run" or "trigger url" — ranked match against tool name + description. Non-billable.

Parameters2

query	string	required	Search query. Forms: "select:name1,name2", "skill:<name>", or free-text keywords.
max_results	integer	optional	Max tools to return for keyword queries (default 5). Ignored for select: and skill: queries.

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query. Forms: \"select:name1,name2\", \"skill:<name>\", or free-text keywords."
    },
    "max_results": {
      "type": "integer",
      "description": "Max tools to return for keyword queries (default 5). Ignored for select: and skill: queries.",
      "default": 5
    }
  },
  "required": [
    "query"
  ]
}

list_skills

List all skill bundles — named groups of tools the agent typically uses together for a single user intent (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.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

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.

Parameters3

monitor	boolean	optional	If set, only return flows where monitor equals this value.
rule_notify_onfail	boolean	optional	If set, filter flows by whether on-fail notifications are enabled.
rule_notify_onmissingdays	boolean	optional	If set, filter flows by whether missing-days notifications are enabled.

Raw schema

{
  "type": "object",
  "properties": {
    "monitor": {
      "type": "boolean",
      "description": "If set, only return flows where monitor equals this value."
    },
    "rule_notify_onfail": {
      "type": "boolean",
      "description": "If set, filter flows by whether on-fail notifications are enabled."
    },
    "rule_notify_onmissingdays": {
      "type": "boolean",
      "description": "If set, filter flows by whether missing-days notifications are enabled."
    }
  }
}

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.

Parameters2

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

get_store_flow_trigger_url

[Requires Pro+ plan] [DEPRECATED — scheduled for removal] Get the trigger URL and trigger type for an HTTP-triggered flow from the Power Clarity cache. Read directly from the stored flow record — no live Power Automate API call is made. Use get_live_flow_trigger_url for a guaranteed-fresh URL.

Parameters2

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    }
  },
  "required": [
    "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 snapshot — not live from the Power Automate API.

Parameters6

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
startTime	string	optional	ISO 8601 start of the time window (default: 7 days ago).
endTime	string	optional	ISO 8601 end of the time window.
status	array	optional	Filter by status. Only the first value is used in the OData filter.
top	number	optional	Maximum number of run rows to return (default 5000).

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "startTime": {
      "type": "string",
      "description": "ISO 8601 start of the time window (default: 7 days ago)."
    },
    "endTime": {
      "type": "string",
      "description": "ISO 8601 end of the time window."
    },
    "status": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "Running",
          "Succeeded",
          "Failed",
          "Cancelled"
        ]
      },
      "description": "Filter by status. Only the first value is used in the OData filter."
    },
    "top": {
      "type": "number",
      "description": "Maximum number of run rows to return (default 5000)."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

get_store_flow_errors

[Requires Pro+ plan] [DEPRECATED — scheduled for removal] Get cached failed run history for a flow from the Power Clarity store (convenience wrapper around get_store_flow_runs with status=Failed). Returns failedActions and remediation hint per run to help diagnose issues. Data is from the stored snapshot — not live from the Power Automate API. Use get_live_flow_runs and filter by status=Failed instead.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
startTime	string	optional	ISO 8601 start of the time window (default: 7 days ago).

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "startTime": {
      "type": "string",
      "description": "ISO 8601 start of the time window (default: 7 days ago)."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

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.

Parameters4

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
startTime	string	optional	ISO 8601 start of the time window (default: 7 days ago).
endTime	string	optional	ISO 8601 end of the time window.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "startTime": {
      "type": "string",
      "description": "ISO 8601 start of the time window (default: 7 days ago)."
    },
    "endTime": {
      "type": "string",
      "description": "ISO 8601 end of the time window."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

set_store_flow_state

[Requires Pro+ plan] [DEPRECATED — scheduled for removal] Start or stop a Power Automate flow via the live Power Automate API, then persists the updated state back to the Power Clarity store. Uses impersonation via a cached service account that is either a flow owner or an environment admin. Returns the updated stored flow record. Use set_live_flow_state instead.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
state	string	required	Desired state for the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "state": {
      "type": "string",
      "enum": [
        "Started",
        "Stopped"
      ],
      "description": "Desired state for the flow."
    }
  },
  "required": [
    "environmentName",
    "flowName",
    "state"
  ]
}

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.

Parameters18

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
description	string	optional
businessImpact	string	optional
businessJustification	string	optional
businessValue	string	optional
ownerTeam	string	optional
ownerBusinessUnit	string	optional
supportGroup	string	optional
supportEmail	string	optional
critical	boolean	optional
monitor	boolean	optional	Enable/disable monitoring for this flow.
rule_notify_onfail	boolean	optional	Send notification when the flow fails.
rule_notify_onmissingdays	number	optional	Send notification when flow has not run for this many days (0 = disabled).
rule_notify_email	string	optional	Comma-separated email addresses for notifications.
tags	string	optional
tier	string	optional
security	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "description": {
      "type": "string"
    },
    "businessImpact": {
      "type": "string"
    },
    "businessJustification": {
      "type": "string"
    },
    "businessValue": {
      "type": "string"
    },
    "ownerTeam": {
      "type": "string"
    },
    "ownerBusinessUnit": {
      "type": "string"
    },
    "supportGroup": {
      "type": "string"
    },
    "supportEmail": {
      "type": "string"
    },
    "critical": {
      "type": "boolean"
    },
    "monitor": {
      "type": "boolean",
      "description": "Enable/disable monitoring for this flow."
    },
    "rule_notify_onfail": {
      "type": "boolean",
      "description": "Send notification when the flow fails."
    },
    "rule_notify_onmissingdays": {
      "type": "number",
      "description": "Send notification when flow has not run for this many days (0 = disabled)."
    },
    "rule_notify_email": {
      "type": "string",
      "description": "Comma-separated email addresses for notifications."
    },
    "tags": {
      "type": "string"
    },
    "tier": {
      "type": "string"
    },
    "security": {
      "type": "string"
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

list_store_environments

[Requires Pro+ plan] List all Power Platform environments from the Power Clarity cache.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

list_store_makers

[Requires Pro+ plan] List all makers (citizen developers / AAD users) from the Power Clarity cache.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

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.

Parameters1

makerKey

string

required

Maker RowKey (AAD object ID of the user).

Raw schema

{
  "type": "object",
  "properties": {
    "makerKey": {
      "type": "string",
      "description": "Maker RowKey (AAD object ID of the user)."
    }
  },
  "required": [
    "makerKey"
  ]
}

list_store_power_apps

[Requires Pro+ plan] List all Power Apps canvas apps from the Power Clarity cache.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

list_store_connections

[Requires Pro+ plan] List all Power Platform connections from the Power Clarity cache.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

get_live_flow_trigger_url

[DEPRECATED — scheduled for removal] Fetch the live trigger URL and method for an HTTP-triggered flow directly from the Power Automate API. Unlike get_flow_trigger_url this calls the PA listCallbackUrl endpoint so the URL is always current. Returns triggerName, triggerType, triggerKind, triggerMethod (e.g. POST) and triggerUrl. For non-HTTP triggers, triggerMethod and triggerUrl are null.

Parameters2

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

get_live_flow_runs

Fetch live run history for a flow directly from the Power Automate API using impersonation — not the cached store. Returns run name, status, startTime, endTime, trigger name/code, and any top-level error.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
top	number	optional	Max runs to return. Paginates automatically. Default 30.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "top": {
      "type": "number",
      "description": "Max runs to return. Paginates automatically. Default 30."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

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.

Parameters4

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
runName	string	required	Run identifier (name field from get_live_flow_runs).
top	number	optional	Max actions to return. Paginates automatically. Omit for all.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "runName": {
      "type": "string",
      "description": "Run identifier (name field from get_live_flow_runs)."
    },
    "top": {
      "type": "number",
      "description": "Max actions to return. Paginates automatically. Omit for all."
    }
  },
  "required": [
    "environmentName",
    "flowName",
    "runName"
  ]
}

get_live_flow_run_action_outputs

Download inputs and outputs for actions in a flow run via SAS blob links from the live Power Automate API. Without actionName: returns top-level actions (optionally filtered by name). With actionName: calls the PA repetitions endpoint to return every execution of that action across all foreach iterations. Each repetition record includes repetitionIndexes (scope name + itemIndex per nesting level), status, error, and the resolved inputs/outputs blobs. Use iterationIndex to pin to a single iteration (matched against the innermost repetitionIndexes[].itemIndex); omit it to return all repetitions.

Parameters6

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
runName	string	required	Run identifier (name field from get_live_flow_runs).
actionName	string	optional	Action name. Without iterationIndex: returns all repetitions of this action across every foreach iteration. With iterationIndex: returns the single repetition matching that iteration. Omit entirely for top-level action list.
iterationIndex	number	optional	Zero-based foreach iteration index. Matched against the innermost repetitionIndexes[].itemIndex in the PA repetition record. Only meaningful when actionName is also set.
top	number	optional	Max actions or repetitions to return. Paginates automatically. Omit for all.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "runName": {
      "type": "string",
      "description": "Run identifier (name field from get_live_flow_runs)."
    },
    "actionName": {
      "type": "string",
      "description": "Action name. Without iterationIndex: returns all repetitions of this action across every foreach iteration. With iterationIndex: returns the single repetition matching that iteration. Omit entirely for top-level action list."
    },
    "iterationIndex": {
      "type": "number",
      "description": "Zero-based foreach iteration index. Matched against the innermost repetitionIndexes[].itemIndex in the PA repetition record. Only meaningful when actionName is also set."
    },
    "top": {
      "type": "number",
      "description": "Max actions or repetitions to return. Paginates automatically. Omit for all."
    }
  },
  "required": [
    "environmentName",
    "flowName",
    "runName"
  ]
}

trigger_live_flow

Trigger an HTTP-triggered Power Automate flow by calling its live callback URL. Fetches the current signed trigger URL via the PA API (listCallbackUrl) then POSTs the provided body to it. If the flow trigger requires Azure Active Directory authentication, the impersonated Bearer token is automatically included — no extra configuration needed. Returns the HTTP status, response body, requiresAadAuth flag, and authType. Only works for flows with a Request (HTTP) trigger type.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
body	object	optional	JSON body to POST to the trigger URL. Omit for flows that expect an empty body.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "body": {
      "type": "object",
      "description": "JSON body to POST to the trigger URL. Omit for flows that expect an empty body."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

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.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
runName	string	required	Run identifier (name field from get_live_flow_runs).

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "runName": {
      "type": "string",
      "description": "Run identifier (name field from get_live_flow_runs)."
    }
  },
  "required": [
    "environmentName",
    "flowName",
    "runName"
  ]
}

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.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
runName	string	required	Run identifier (name field from get_live_flow_runs).

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "runName": {
      "type": "string",
      "description": "Run identifier (name field from get_live_flow_runs)."
    }
  },
  "required": [
    "environmentName",
    "flowName",
    "runName"
  ]
}

set_live_flow_state

Start or stop a Power Automate flow via the live Power Automate API using an impersonated service account. Does not require a Power Clarity workspace — works for any flow the impersonated account can access. Reads the current flow state first and only issues the start/stop call if a state change is actually needed. Returns the flow name, environment, requested state, and the actual state reported by the PA API after the operation.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.
state	string	required	Desired state for the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    },
    "state": {
      "type": "string",
      "enum": [
        "Started",
        "Stopped"
      ],
      "description": "Desired state for the flow."
    }
  },
  "required": [
    "environmentName",
    "flowName",
    "state"
  ]
}

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.

Parameters2

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

update_live_flow

Update or create a Power Automate flow via the live PA API. If flowName is omitted or blank, a new flow is created (PUT with a generated GUID) using an environment admin account — definition and displayName are required in that case. If flowName is provided, the existing flow is PATCHed: displayName and/or definition and/or connectionReferences are updated. Mirrors displayName changes into the Power Clarity cache (gFlows). To modify a definition: call get_live_flow, mutate properties.definition (including its description), pass it here. The flow description lives at definition.description and is required; we append " #flowstudio-mcp" to it for usage tracking.

Parameters5

environmentName	string	required	Name of the Power Platform environment.
flowName	string	optional	Name (ID) of the flow to update. Omit or leave blank to create a new flow.
displayName	string	optional	Display name for the flow. Required when creating.
definition	object	optional	Full flow definition as a JSON object (triggers + actions + parameters + outputs + description). MUST be a JSON object — strings are rejected. Do not JSON.stringify the definition; pass the parsed object directly. Required when creating. For updates, obtain from get_live_flow (properties.definition), modify it, then pass the modified object here. definition.description is required (a short note about what changed); when updating, if you omit it we reuse the flow's existing description.
connectionReferences	object	optional	Connection references map — keyed by logical name (e.g. shared_sharepointonline), each value is { connectionName, id }. Goes into properties.connectionReferences on the PA API call.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow to update. Omit or leave blank to create a new flow."
    },
    "displayName": {
      "type": "string",
      "description": "Display name for the flow. Required when creating."
    },
    "definition": {
      "type": "object",
      "description": "Full flow definition as a JSON object (triggers + actions + parameters + outputs + description). MUST be a JSON object — strings are rejected. Do not JSON.stringify the definition; pass the parsed object directly. Required when creating. For updates, obtain from get_live_flow (properties.definition), modify it, then pass the modified object here. definition.description is required (a short note about what changed); when updating, if you omit it we reuse the flow's existing description."
    },
    "connectionReferences": {
      "type": "object",
      "description": "Connection references map — keyed by logical name (e.g. shared_sharepointonline), each value is { connectionName, id }. Goes into properties.connectionReferences on the PA API call."
    }
  },
  "required": [
    "environmentName"
  ]
}

get_live_flow_http_schema

[DEPRECATED — scheduled for removal] Inspect the HTTP interface of a Power Automate Request-triggered flow: returns the JSON schema the trigger URL expects as the POST body, any required headers, the HTTP method, and the JSON schema(s) defined on any Response action(s) in the flow. All information is read from the live flow definition via the PA API — no test call is made to the trigger URL. Use this before calling trigger_live_flow to understand what body to send.

Parameters2

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

list_live_environments

List all Power Platform environments directly from the Power Automate API — not the cached store. Returns id, displayName, sku, location, and state for each environment visible to the impersonated service account.

Parameters1

top

number

optional

Max environments to return. Paginates automatically. Omit for all.

Raw schema

{
  "type": "object",
  "properties": {
    "top": {
      "type": "number",
      "description": "Max environments to return. Paginates automatically. Omit for all."
    }
  }
}

list_live_flows

List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows owned by AND shared with the impersonated account (personal + team), with full definitions. mode=admin: all flows in the environment (requires an admin account). 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.

Parameters6

environmentName	string	required	Name of the Power Platform environment.
mode	string	optional	owner (default): user-scoped — owned + shared-with-me flows (personal + team), with full definitions. admin: admin-scoped endpoint, all flows.
top	number	optional	Max flows to return. Paginates automatically. Omit for all.
search	string	optional	Optional case-insensitive filter applied to flow displayName.
continuationUrl	string	optional	nextLink value returned by a previous call. Pass to resume pagination from where the last call stopped. Must match the same mode as the original call.
timeoutSeconds	number	optional	Stop collecting pages after this many seconds and return a nextLink for the next batch. Default 25. Max 55.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "mode": {
      "type": "string",
      "enum": [
        "owner",
        "admin"
      ],
      "description": "owner (default): user-scoped — owned + shared-with-me flows (personal + team), with full definitions. admin: admin-scoped endpoint, all flows."
    },
    "top": {
      "type": "number",
      "description": "Max flows to return. Paginates automatically. Omit for all."
    },
    "search": {
      "type": "string",
      "description": "Optional case-insensitive filter applied to flow displayName."
    },
    "continuationUrl": {
      "type": "string",
      "description": "nextLink value returned by a previous call. Pass to resume pagination from where the last call stopped. Must match the same mode as the original call."
    },
    "timeoutSeconds": {
      "type": "number",
      "description": "Stop collecting pages after this many seconds and return a nextLink for the next batch. Default 25. Max 55."
    }
  },
  "required": [
    "environmentName"
  ]
}

list_live_connections

List Power Platform connections in an environment directly from the Power Automate API — not the cached store. 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.

Parameters3

environmentName	string	optional	Name of the Power Platform environment. Omit to list connections across all environments.
top	number	optional	Max connections to return. Paginates automatically. Omit for all.
search	string	optional	Optional case-insensitive substring filter applied to id, displayName, connectorName, and accountName. Adds connectionReferenceTemplate + hostTemplate to each returned connection.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment. Omit to list connections across all environments."
    },
    "top": {
      "type": "number",
      "description": "Max connections to return. Paginates automatically. Omit for all."
    },
    "search": {
      "type": "string",
      "description": "Optional case-insensitive substring filter applied to id, displayName, connectorName, and accountName. Adds connectionReferenceTemplate + hostTemplate to each returned connection."
    }
  },
  "required": []
}

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.

Parameters9

environmentName	string	required	Name of the Power Platform environment.
connectorName	string	optional	Connector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search.
apiName	string	optional	Alias for connectorName, matching Canvas MCP describe_api naming.
mode	string	optional	summary (default): compact operation catalog. full: raw OpenAPI metadata.
operationId	string	optional	Optional operation ID to describe with expanded inputs and outputs.
type	string	optional	Operation usage to include in summary mode. Default Action.
search	string	optional	Optional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors.
top	number	optional	Max operations to return in connector summary mode, or max top search results to show in cross-connector search. Default 250 for summary, 10 for search display.
variant	string	optional	When an operation has multiple authored variants (e.g. shared_teams/PostMessageToConversation has channel/groupchat/flowbot_chat), pass a specific variantKey to get that variant's hint and exampleDefinition. Omit to receive a hint listing the available variants.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "connectorName": {
      "type": "string",
      "description": "Connector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search."
    },
    "apiName": {
      "type": "string",
      "description": "Alias for connectorName, matching Canvas MCP describe_api naming."
    },
    "mode": {
      "type": "string",
      "enum": [
        "summary",
        "full"
      ],
      "description": "summary (default): compact operation catalog. full: raw OpenAPI metadata."
    },
    "operationId": {
      "type": "string",
      "description": "Optional operation ID to describe with expanded inputs and outputs."
    },
    "type": {
      "type": "string",
      "enum": [
        "Action",
        "Trigger"
      ],
      "description": "Operation usage to include in summary mode. Default Action."
    },
    "search": {
      "type": "string",
      "description": "Optional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors."
    },
    "top": {
      "type": "number",
      "description": "Max operations to return in connector summary mode, or max top search results to show in cross-connector search. Default 250 for summary, 10 for search display."
    },
    "variant": {
      "type": "string",
      "description": "When an operation has multiple authored variants (e.g. shared_teams/PostMessageToConversation has channel/groupchat/flowbot_chat), pass a specific variantKey to get that variant's hint and exampleDefinition. Omit to receive a hint listing the available variants."
    }
  },
  "required": [
    "environmentName"
  ]
}

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.

Parameters8

environmentName	string	required	Name of the Power Platform environment.
connectorName	string	optional	Connector logical name, for example shared_teams.
apiName	string	optional	Alias for connectorName.
operationId	string	optional	Operation ID that owns the dynamic parameter.
parameterName	string	required	Dynamic parameter name, for example groupId or channelId.
connectionName	string	required	Required connector connection name/id, for example shared-teams-{guid}. Choose the connection that the flow action should run as. Use list_live_connections to find candidates.
parameters	object	optional	Resolved dependent parameter values, for example { "groupId": "<team id>" }.
dynamicMetadata	object	required	x-ms-dynamic-list or x-ms-dynamic-values metadata from describe_live_connector.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "connectorName": {
      "type": "string",
      "description": "Connector logical name, for example shared_teams."
    },
    "apiName": {
      "type": "string",
      "description": "Alias for connectorName."
    },
    "operationId": {
      "type": "string",
      "description": "Operation ID that owns the dynamic parameter."
    },
    "parameterName": {
      "type": "string",
      "description": "Dynamic parameter name, for example groupId or channelId."
    },
    "connectionName": {
      "type": "string",
      "description": "Required connector connection name/id, for example shared-teams-{guid}. Choose the connection that the flow action should run as. Use list_live_connections to find candidates."
    },
    "parameters": {
      "type": "object",
      "description": "Resolved dependent parameter values, for example { \"groupId\": \"<team id>\" }."
    },
    "dynamicMetadata": {
      "type": "object",
      "description": "x-ms-dynamic-list or x-ms-dynamic-values metadata from describe_live_connector."
    }
  },
  "required": [
    "environmentName",
    "parameterName",
    "connectionName",
    "dynamicMetadata"
  ]
}

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.

Parameters12

environmentName	string	required	Name of the Power Platform environment.
connectorName	string	optional	Connector logical name, for example shared_sharepointonline.
apiName	string	optional	Alias for connectorName.
operationId	string	optional	Operation ID that owns the dynamic parameter.
parameterName	string	required	Dynamic properties parameter name, for example item or body.
connectionName	string	required	Required connector connection name/id. Use list_live_connections to find candidates.
parameters	object	optional	Resolved dependent parameter values, for example { "dataset": "<site url>", "table": "<list id>" }.
dynamicMetadata	object	required	x-ms-dynamic-properties or x-ms-dynamic-schema metadata from describe_live_connector.
contextParameterAlias	string	optional	Alias for returned property paths. Defaults to the parameter alias from metadata, or parameterName.
location	string	optional	Whether to resolve input or output dynamic properties. Default input.
propertyName	string	optional	Optional property name/title/alias to return just one property. Useful for a progressive follow-up with includeRaw=true after inspecting the compact schema.
includeRaw	boolean	optional	Include raw schema/property definitions. With propertyName, includes raw only for the matched property. Without propertyName, includes the full raw schema. Default false.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "connectorName": {
      "type": "string",
      "description": "Connector logical name, for example shared_sharepointonline."
    },
    "apiName": {
      "type": "string",
      "description": "Alias for connectorName."
    },
    "operationId": {
      "type": "string",
      "description": "Operation ID that owns the dynamic parameter."
    },
    "parameterName": {
      "type": "string",
      "description": "Dynamic properties parameter name, for example item or body."
    },
    "connectionName": {
      "type": "string",
      "description": "Required connector connection name/id. Use list_live_connections to find candidates."
    },
    "parameters": {
      "type": "object",
      "description": "Resolved dependent parameter values, for example { \"dataset\": \"<site url>\", \"table\": \"<list id>\" }."
    },
    "dynamicMetadata": {
      "type": "object",
      "description": "x-ms-dynamic-properties or x-ms-dynamic-schema metadata from describe_live_connector."
    },
    "contextParameterAlias": {
      "type": "string",
      "description": "Alias for returned property paths. Defaults to the parameter alias from metadata, or parameterName."
    },
    "location": {
      "type": "string",
      "enum": [
        "input",
        "output"
      ],
      "description": "Whether to resolve input or output dynamic properties. Default input."
    },
    "propertyName": {
      "type": "string",
      "description": "Optional property name/title/alias to return just one property. Useful for a progressive follow-up with includeRaw=true after inspecting the compact schema."
    },
    "includeRaw": {
      "type": "boolean",
      "description": "Include raw schema/property definitions. With propertyName, includes raw only for the matched property. Without propertyName, includes the full raw schema. Default false."
    }
  },
  "required": [
    "environmentName",
    "parameterName",
    "connectionName",
    "dynamicMetadata"
  ]
}

add_live_flow_to_solution

Migrate a non-solution Power Automate flow into a solution via the admin migrateFlows API. If the flow is already part of a solution, returns an error message without attempting migration. solutionId is optional — omit to migrate into the default solution.

Parameters3

environmentName	string	required	Name of the Power Platform environment.
flowName	string	required	Name (ID) of the flow to migrate into the solution.
solutionId	string	optional	Target solution ID (Dataverse solutionid GUID). Omit for the default solution. Discover IDs via get_live_dynamic_options on shared_commondataserviceforapps/ListRecords with entityName "solutions" (value-path solutionid, value-title friendlyname); needs a Dataverse connection in the env.

Raw schema

{
  "type": "object",
  "properties": {
    "environmentName": {
      "type": "string",
      "description": "Name of the Power Platform environment."
    },
    "flowName": {
      "type": "string",
      "description": "Name (ID) of the flow to migrate into the solution."
    },
    "solutionId": {
      "type": "string",
      "description": "Target solution ID (Dataverse solutionid GUID). Omit for the default solution. Discover IDs via get_live_dynamic_options on shared_commondataserviceforapps/ListRecords with entityName \"solutions\" (value-path solutionid, value-title friendlyname); needs a Dataverse connection in the env."
    }
  },
  "required": [
    "environmentName",
    "flowName"
  ]
}

README.md11 KBView on GitHub

FlowStudio MCP — Power Automate Skills for AI Agents

Give your AI agent the same visibility you have in the Power Automate portal — plus a bit more. The Graph API only returns top-level run status — agents can't see action inputs, loop iterations, or nested failures. FlowStudio MCP exposes all of it.

Agent debugging a Power Automate flow via MCP

You can click through the portal and find the root cause. Your agent can't — unless it has MCP.

The portal shows everything to a human — but agents only see the top-level error via Graph API

With FlowStudio MCP, the agent sees what you see

When you need this

Your agent can see that a flow failed, but not why — Graph API only returns status codes
You want your agent to see action-level inputs and outputs, like you can in the portal
A loop has hundreds of iterations and some produced bad output — in the portal you'd click through each one, but the agent can scan all iteration inputs and outputs at once
You want to check flow health, failure rates, and maker activity across your tenant without opening the admin center
You need to classify flows, detect orphaned resources, or audit connectors at scale — without installing the CoE Starter Kit
You're tired of being the middle-man between your agent and the portal

Graph API vs FlowStudio MCP

The core difference: Graph API gives your agent run status. MCP gives your agent the inputs and outputs of every action.

What the agent sees	Graph API	FlowStudio MCP
Run passed or failed	Yes	Yes
Action inputs and outputs	No	Yes
Error details beyond status code	No	Yes
Child flow run details	No	Yes
Loop iteration data	No	Yes
Flow definition (read + write)	Limited	Full JSON
Resubmit / cancel runs	Limited	Yes
Cached flow health & failure rates	No	Yes
Maker / Power Apps / connection inventory	No	Yes
Governance metadata (tags, impact, owner)	No	Yes

Skills

Skill	Description
`power-automate-mcp`	Connect to and operate Power Automate cloud flows — list flows, read definitions, check runs, resubmit, cancel
`power-automate-debug`	Step-by-step diagnostic process for investigating failing flows
`power-automate-build`	Build, scaffold, and deploy Power Automate flow definitions from scratch
`power-automate-monitoring`	Flow health, failure rates, maker inventory, Power Apps, environment and connection counts
`power-automate-governance`	Classify flows by impact, detect orphans, audit connectors, manage notifications, compute archive scores

The first three skills use live Power Automate API calls. The monitoring and governance skills use the cached store — a daily snapshot with aggregated stats, remediation hints, and governance metadata. Requires a FlowStudio for Teams or MCP Pro+ subscription for store tools.

Each skill follows the Agent Skills specification and works with any compatible agent.

Supported agents

Copilot, Claude Code, ChatGPT, Codex, OpenClaw, Gemini CLI, Cursor, Goose, Amp, OpenHands

Guides

Full walkthroughs on learn.flowstudio.app:

Getting started — install FlowStudio MCP for any agent
Build flows with AI agents — a worked 3-step example
Vibe code Power Automate — describe the flow, the agent builds it
Power Automate in VS Code — work on flows from your editor
Debug a failing flow — find the root cause from action-level data
By agent: ChatGPT · Claude · GitHub Copilot · Copilot Studio · Codex

Quick Start

Connect from ChatGPT or claude.ai

Sign in with your Microsoft account instead of pasting a key. Add https://mcp.flowstudio.app/mcp/oauth as a connector in ChatGPT (Developer mode on) or at claude.ai, then follow the sign-in prompt. Walkthrough: ChatGPT for Power Automate.

Install as Claude Code plugin

Available through the Claude plugin marketplace after approval. To test locally:

bash

git clone https://github.com/ninihen1/power-automate-mcp-skills.git
claude --plugin-dir ./power-automate-mcp-skills

Then connect the MCP server:

bash

claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
  --header "x-api-key: <YOUR_TOKEN>"

Get your token at mcp.flowstudio.app.

Install in Codex

Inside a Codex session, install skills directly:

code

$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-mcp
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-debug
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-build
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-monitoring
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-governance

Then connect the MCP server in ~/.codex/config.toml:

toml

[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"

[mcp_servers.flowstudio.http_headers]
x-api-key = "<YOUR_TOKEN>"

Install via skills.sh

Search for flowstudio on skills.sh, or:

bash

npx skills add github/awesome-copilot -s flowstudio-power-automate-mcp
npx skills add github/awesome-copilot -s flowstudio-power-automate-debug
npx skills add github/awesome-copilot -s flowstudio-power-automate-build
npx skills add github/awesome-copilot -s flowstudio-power-automate-monitoring
npx skills add github/awesome-copilot -s flowstudio-power-automate-governance

Install via ClawHub

bash

npx clawhub@latest install power-automate-mcp

Install via Smithery

bash

npx smithery skill add flowstudio/power-automate-mcp

Manual install

Copy the skill folder(s) into your project's .github/skills/ directory (or wherever your agent discovers skills).

Connect the MCP server

Claude Code:

bash

claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
  --header "x-api-key: <YOUR_TOKEN>"

Codex (~/.codex/config.toml):

toml

[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"

[mcp_servers.flowstudio.http_headers]
x-api-key = "<YOUR_TOKEN>"

Copilot / VS Code (.vscode/mcp.json):

json

{
  "servers": {
    "flowstudio": {
      "type": "http",
      "url": "https://mcp.flowstudio.app/mcp",
      "headers": { "x-api-key": "<YOUR_TOKEN>" }
    }
  }
}

Get your token at mcp.flowstudio.app.

Real debugging examples

These are from real production investigations, not demos.

Expression error in child flow — contains(string(...)) crashed on a nested property. Agent traced through parent flow, into child, through loop iterations, and found the failing input. Portal showed "ExpressionEvaluationFailed" with no context.
Data entry, not a flow bug — User reported two "bugs" back to back. Agent proved both were data entry errors (missing comma in email, single address in CC field). Flow was correct. Diagnosed in seconds.
Null value crashes child flow — split(Name, ', ') crashed when 38% of records had null Names. Agent traced parent to child to loop to action, found the root cause, and deployed a fix via update_live_flow.

Prerequisites

A FlowStudio MCP subscription (all live tools)
For store tools (monitoring, governance): FlowStudio for Teams or MCP Pro+
MCP endpoint: https://mcp.flowstudio.app/mcp
API key / JWT token (passed as x-api-key header)

Repository structure

code

skills/
  power-automate-mcp/          core connection & operation skill
  power-automate-debug/        debug workflow skill
  power-automate-build/        build & deploy skill
  power-automate-monitoring/   flow health & tenant inventory skill
  power-automate-governance/   compliance & governance skill
examples/                      real debugging walkthroughs
README.md
LICENSE                        MIT

Available on GitHub

Works with Copilot, Claude, ChatGPT, and any MCP-compatible agent.

awesome-copilot (merged)
skills.sh (3K+ installs)
Smithery (published)
ClawHub (v1.1.0)

Contributing

Contributions welcome. Each skill folder must contain a SKILL.md with the required frontmatter. See the existing skills for the format.

License

MIT

Keywords: Power Automate debugging, flow run history, expression evaluation failed, child flow failure, nested action errors, loop iteration output, agent automation MCP, Power Platform AI, flow definition deploy, resubmit failed run, flow monitoring, governance, CoE, orphan detection, connector audit, archive score, maker inventory

Install

Tools (33)

tool_searchlist_skillslist_store_flowsget_store_flowget_store_flow_trigger_urlget_store_flow_runsget_store_flow_errorsget_store_flow_summary

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.flowstudio.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "flowstudio-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.flowstudio.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

FlowStudio MCP (io.github.ninihen1/flowstudio-mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

tool_search

list_skills

list_store_flows

get_store_flow

get_store_flow_trigger_url

get_store_flow_runs

get_store_flow_errors

get_store_flow_summary

set_store_flow_state

update_store_flow

list_store_environments

list_store_makers

get_store_maker

list_store_power_apps

list_store_connections

get_live_flow_trigger_url

get_live_flow_runs

get_live_flow_run_error

get_live_flow_run_action_outputs

trigger_live_flow

cancel_live_flow_run

resubmit_live_flow_run

set_live_flow_state

get_live_flow

update_live_flow

get_live_flow_http_schema

list_live_environments

list_live_flows

list_live_connections

describe_live_connector

get_live_dynamic_options

get_live_dynamic_properties

add_live_flow_to_solution

FlowStudio MCP — Power Automate Skills for AI Agents

When you need this

Graph API vs FlowStudio MCP

Skills

Supported agents

Guides

Quick Start

Connect from ChatGPT or claude.ai

Install as Claude Code plugin

Install in Codex

Install via skills.sh

Install via ClawHub

Install via Smithery

Manual install

Connect the MCP server

Real debugging examples

Prerequisites

Repository structure

Available on GitHub

Contributing

License

Install

Remote endpoint

Related servers