Power Automate MCP Server by Flow Studio
REMOTE · MCP.FLOWSTUDIO.APP · SCANNED SEP 20
Debug, build, and manage Power Automate cloud flows with AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5730 tokens (~197/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management84
- Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the Power Automate MCP Server by Flow Studio server?
Power Automate MCP Server by Flow Studio is a hosted endpoint at https://mcp.flowstudio.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.flowstudio.app
claude mcp add --transport http ninihen1-flowstudio-mcp 'https://mcp.flowstudio.app/mcp'
{
"mcpServers": {
"ninihen1-flowstudio-mcp": {
"url": "https://mcp.flowstudio.app/mcp"
}
}
} {
"servers": {
"ninihen1-flowstudio-mcp": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp"
}
}
} [mcp_servers.ninihen1-flowstudio-mcp] url = "https://mcp.flowstudio.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ninihen1-flowstudio-mcp": {
"type": "remote",
"url": "https://mcp.flowstudio.app/mcp",
"enabled": true
}
}
} openclaw mcp add ninihen1-flowstudio-mcp --url 'https://mcp.flowstudio.app/mcp' --transport streamable-http
mcp_servers:
ninihen1-flowstudio-mcp:
url: "https://mcp.flowstudio.app/mcp" {
"McpServers": {
"ninihen1-flowstudio-mcp": {
"Transport": "http",
"Url": "https://mcp.flowstudio.app/mcp"
}
}
} assistant mcp add ninihen1-flowstudio-mcp -t streamable-http -u 'https://mcp.flowstudio.app/mcp'
{
"mcpServers": {
"ninihen1-flowstudio-mcp": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Sept 26 0
- Server version: 1.3.25 → 1.3.31 functional
- 15 Sept 26 0
- Server version: 1.3.24 → 1.3.25 functional
- 11 Sept 26 −2
- Tool “get_live_flow_http_schema” was removed ▼ security
- Tool “get_live_flow_trigger_url” was removed ▼ security
- Tool “get_store_flow_errors” was removed ▼ security
- Tool “get_store_flow_trigger_url” was removed ▼ security
- Tool “set_store_flow_state” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “add_live_flow_to_solution” rewrote its description, which is the text the model reads security
- Tool “get_live_flow_run_action_outputs” rewrote its description, which is the text the model reads security
- Tool “set_live_flow_state” rewrote its description, which is the text the model reads security
- Tool “tool_search” rewrote its description, which is the text the model reads security
- Tool “trigger_live_flow” rewrote its description, which is the text the model reads security
- Tool “update_live_flow” rewrote its description, which is the text the model reads security
- Schema quality: 6809 → 5730 ▲ functional
- Server version: 1.3.20 → 1.3.24 functional
- 8 Sept 26 0
- Server version: 1.3.18 → 1.3.20 functional
- 7 Sept 26 0
- Tool “list_live_environments” rewrote its description, which is the text the model reads security
- Tool “list_live_flows” rewrote its description, which is the text the model reads security
- Server version: 1.2.83 → 1.3.18 functional
- “list_live_flows” added an optional parameter “includeDeleted” cosmetic
- “list_live_environments” reworded the description of “mode” cosmetic
- 6 Sept 26 0
- Tool “get_live_flow_run_action_outputs” rewrote its description, which is the text the model reads security
- Tool “get_live_flow_runs” rewrote its description, which is the text the model reads security
- Server version: 1.2.77 → 1.2.83 functional
- “get_live_flow_run_action_outputs” added an optional parameter “checkId” cosmetic
- “get_live_flow_run_action_outputs” added an optional parameter “trigger” cosmetic
- “get_live_flow_runs” added an optional parameter “includeTriggerChecks” cosmetic
- “get_live_flow_run_action_outputs” reworded the description of “runName” cosmetic
- “get_live_flow_run_action_outputs” made “runName” optional cosmetic
- 4 Sept 26 0
- Tool “list_live_environments” rewrote its description, which is the text the model reads security
- Tool “trigger_live_flow” rewrote its description, which is the text the model reads security
- Tool “update_live_flow” rewrote its description, which is the text the model reads security
- Server version: 1.2.70 → 1.2.77 functional
- “list_live_environments” added an optional parameter “mode” cosmetic
- “update_live_flow” reworded the description of “connectionReferences” cosmetic
- 3 Sept 26 0
- Server version: 1.2.66 → 1.2.70 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.flowstudio.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=flowstudio.app | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7f3c176930f41ba80eb5618bbe1719f4 |
| SANs: flowstudio.app, *.flowstudio.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.flowstudio.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| flowstudio.app. | present | 2371 | 13 | Verified |
| mcp.flowstudio.app. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Flow Studio MCP", ApiKey realm="Flow Studio MCP", header="x-api-key"
Bearer realm="Flow Studio MCP", ApiKey realm="Flow Studio MCP", header="x-api-key" Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.flowstudio.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.flowstudio.app/mcp | HTTPS enforced | 301 | https://mcp.flowstudio.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_live_flow_to_solution ~140
Move a flow into a solution. Refuses if the flow is already in one. solutionId is optional — omit for the default solution.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow to migrate into the solution. |
| solutionId | string | – | 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" (va… |
No output schema declared.
No examples provided.
cancel_live_flow_run ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| runName | string | yes | Run identifier (name field from get_live_flow_runs). |
No output schema declared.
No examples provided.
describe_live_connector ~374
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiName | string | – | Alias for connectorName, matching Canvas MCP describe_api naming. |
| connectorName | string | – | Connector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search. |
| environmentName | string | yes | Name of the Power Platform environment. |
| mode | string | – | summary (default): compact operation catalog. full: raw OpenAPI metadata. |
| operationId | string | – | Optional operation ID to describe with expanded inputs and outputs. |
| search | string | – | Optional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors. |
| top | number | – | 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. |
| type | string | – | Operation usage to include in summary mode. Default Action. |
| variant | string | – | 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 exampleDef… |
No output schema declared.
No examples provided.
get_live_dynamic_options ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiName | string | – | Alias for connectorName. |
| connectionName | string | yes | 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. |
| connectorName | string | – | Connector logical name, for example shared_teams. |
| dynamicMetadata | object | yes | x-ms-dynamic-list or x-ms-dynamic-values metadata from describe_live_connector. |
| environmentName | string | yes | Name of the Power Platform environment. |
| operationId | string | – | Operation ID that owns the dynamic parameter. |
| parameterName | string | yes | Dynamic parameter name, for example groupId or channelId. |
| parameters | object | – | Resolved dependent parameter values, for example { "groupId": "<team id>" }. |
No output schema declared.
No examples provided.
get_live_dynamic_properties ~339
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiName | string | – | Alias for connectorName. |
| connectionName | string | yes | Required connector connection name/id. Use list_live_connections to find candidates. |
| connectorName | string | – | Connector logical name, for example shared_sharepointonline. |
| contextParameterAlias | string | – | Alias for returned property paths. Defaults to the parameter alias from metadata, or parameterName. |
| dynamicMetadata | object | yes | x-ms-dynamic-properties or x-ms-dynamic-schema metadata from describe_live_connector. |
| environmentName | string | yes | Name of the Power Platform environment. |
| includeRaw | boolean | – | Include raw schema/property definitions. With propertyName, includes raw only for the matched property. Without propertyName, includes the full raw schema. Default false. |
| location | string | – | Whether to resolve input or output dynamic properties. Default input. |
| operationId | string | – | Operation ID that owns the dynamic parameter. |
| parameterName | string | yes | Dynamic properties parameter name, for example item or body. |
| parameters | object | – | Resolved dependent parameter values, for example { "dataset": "<site url>", "table": "<list id>" }. |
| propertyName | string | – | Optional property name/title/alias to return just one property. Useful for a progressive follow-up with includeRaw=true after inspecting the compact schema. |
No output schema declared.
No examples provided.
get_live_flow ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
No output schema declared.
No examples provided.
get_live_flow_run_action_outputs ~412
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, status, error, and resolved inputs/outputs. Use iterationIndex to pin one iteration; omit it for all. TRIGGER PAYLOADS: set trigger=true with a runName to get that run's trigger inputs and outputs. No Compose workaround is needed. TRIGGER CHECKS: pass checkId (from get_live_flow_runs -> triggerChecks.recent[].checkId) to read a trigger evaluation that never became a run — that is how you see WHY a trigger is failing. Do not supply runName with a checkId.
| Name | Type | Req | Description |
|---|---|---|---|
| actionName | string | – | 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 f… |
| checkId | string | – | Trigger check id (checkId from get_live_flow_runs -> triggerChecks). Returns that check's inputs/outputs, including the failure reason. Not a run id — the two are different, which is why a check id r… |
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| iterationIndex | number | – | Zero-based foreach iteration index. Matched against the innermost repetitionIndexes[].itemIndex in the PA repetition record. Only meaningful when actionName is also set. |
| runName | string | – | Run identifier (name field from get_live_flow_runs). Required unless checkId is given. |
| top | number | – | Max actions or repetitions to return. Paginates automatically. Omit for all. |
| trigger | boolean | – | Return the RUN's trigger inputs/outputs instead of its actions. Requires runName. |
No output schema declared.
No examples provided.
get_live_flow_run_error ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| runName | string | yes | Run identifier (name field from get_live_flow_runs). |
| top | number | – | Max actions to return. Paginates automatically. Omit for all. |
No output schema declared.
No examples provided.
get_live_flow_runs ~227
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 healthy. A trigger that fires and evaluates to nothing, or fails to evaluate, records a TRIGGER CHECK and never becomes a run. When there are no runs (or when includeTriggerChecks is set) this tool also reports the trigger check history, so "nothing ran" can be told apart from "the trigger has been failing". Read triggerChecks.byStatus before concluding a flow is fine.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| includeTriggerChecks | boolean | – | Also report trigger check history when runs DO exist. Checks are always reported when there are no runs. Costs two extra API calls. |
| top | number | – | Max runs to return. Paginates automatically. Default 30. |
No output schema declared.
No examples provided.
get_store_flow ~92
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
No output schema declared.
No examples provided.
get_store_flow_runs ~187
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | string | – | ISO 8601 end of the time window. |
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| startTime | string | – | ISO 8601 start of the time window (default: 7 days ago). |
| status | array | – | Filter by status. Only the first value is used in the OData filter. |
| top | number | – | Maximum number of run rows to return (default 5000). |
No output schema declared.
No examples provided.
get_store_flow_summary ~140
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| endTime | string | – | ISO 8601 end of the time window. |
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| startTime | string | – | ISO 8601 start of the time window (default: 7 days ago). |
No output schema declared.
No examples provided.
get_store_maker ~69
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| makerKey | string | yes | Maker RowKey (AAD object ID of the user). |
No output schema declared.
No examples provided.
list_live_connections ~213
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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Required. Name of the Power Platform environment (a GUID, or a name like "Default-<tid>"). Call list_live_environments if you do not have one — the platform cannot list connections across environment… |
| search | string | – | Optional case-insensitive substring filter applied to id, displayName, connectorName, and accountName. Adds connectionReferenceTemplate + hostTemplate to each returned connection. |
| top | number | – | Max connections to RETURN, applied after search. Paginates automatically. Omit for all. |
No output schema declared.
No examples provided.
list_live_environments ~192
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: only those you administer; errors rather than guessing if admin access cannot be determined. isAdmin means you hold the ListAnyFlow permission there — the capability list_live_flows mode=admin needs. It is null, never false, when the platform did not tell us. isMember is true for every environment returned.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | all (default) and member: every environment you belong to. admin: only those where you hold ListAnyFlow; errors rather than returning a shorter list if admin access cannot be determined. |
| top | number | – | Max environments to return. Paginates automatically. Omit for all. |
No output schema declared.
No examples provided.
list_live_flows ~356
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=admin: all flows in the environment (requires an admin account). mode=admin with includeDeleted=true also returns soft-deleted flows (state=Deleted) — the only way to find a deleted flow. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| continuationUrl | string | – | 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. |
| environmentName | string | yes | Name of the Power Platform environment. |
| includeDeleted | boolean | – | Include soft-deleted flows, which come back with state=Deleted and can be restored with restore_live_flow. Requires mode=admin — the user-scoped listing never returns deleted flows. Off by default. |
| mode | string | – | owner (default): user-scoped — owned + shared-with-me flows (personal + team), with full definitions. admin: admin-scoped endpoint, all flows. |
| search | string | – | Optional case-insensitive filter applied to flow displayName. |
| timeoutSeconds | number | – | Stop collecting pages after this many seconds and return a nextLink for the next batch. Default 25. Max 55. |
| top | number | – | Max flows to return. Paginates automatically. Omit for all. |
No output schema declared.
No examples provided.
list_skills ~96
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 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_store_connections ~27
[Requires Pro+ plan] List all Power Platform connections from the Power Clarity cache.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_store_environments ~28
[Requires Pro+ plan] List all Power Platform environments from the Power Clarity cache.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_store_flows ~134
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor | boolean | – | If set, only return flows where monitor equals this value. |
| rule_notify_onfail | boolean | – | If set, filter flows by whether on-fail notifications are enabled. |
| rule_notify_onmissingdays | boolean | – | If set, filter flows by whether missing-days notifications are enabled. |
No output schema declared.
No examples provided.
list_store_makers ~35
[Requires Pro+ plan] List all makers (citizen developers / AAD users) from the Power Clarity cache.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_store_power_apps ~29
[Requires Pro+ plan] List all Power Apps canvas apps from the Power Clarity cache.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_bug ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| category | string | – | – |
| chunk | integer | – | Optional. Omit to append the next chunk automatically. |
| contact_email | string | – | – |
| content | string | – | Text attachment body. Max 64 KB per call. |
| content_base64 | string | – | Binary attachment body, base64-encoded. Max 256 KB decoded per call. Use for images/PDF; pass text through `content` instead. Do not send both. |
| content_type | string | – | Media type of the attachment. text/plain (default), text/csv, text/markdown, application/json, application/har+json, application/xml, image/png, image/jpeg, image/gif, image/webp, application/pdf. |
| details | string | – | – |
| environment_name | string | – | – |
| file_name | string | – | – |
| final_chunk | boolean | – | – |
| flow_name | string | – | – |
| include_diagnostics | boolean | – | – |
| notify | boolean | – | – |
| severity | string | – | – |
| summary | string | – | – |
| ticket | string | – | – |
| tool_name | string | – | – |
No output schema declared.
No examples provided.
resubmit_live_flow_run ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| runName | string | yes | Run identifier (name field from get_live_flow_runs). |
No output schema declared.
No examples provided.
set_live_flow_state ~77
Start or stop the flow you name. Reads the current state first and only calls Power Automate if a change is actually needed.
| Name | Type | Req | Description |
|---|---|---|---|
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| state | string | yes | Desired state for the flow. |
No output schema declared.
No examples provided.
tool_search ~144
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 run" — ranked against name and description. Non-billable.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Max tools to return for keyword queries (default 5). Ignored for select: and skill: queries. |
| query | string | yes | Search query. Forms: "select:name1,name2", "skill:<name>", or free-text keywords. |
No output schema declared.
No examples provided.
trigger_live_flow ~143
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 passing `body` to one is refused. Pass trigger inputs as `body`. Automated connector triggers only fire from their source event.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON body to POST to the trigger URL. Omit for flows that expect an empty body. |
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
No output schema declared.
No examples provided.
update_live_flow ~767
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. SURGICAL EDIT: pass `operations` — an ordered list of set/add/remove/merge ops on array-of-keys paths — to change one action or parameter without resending the whole definition. Provide EITHER operations OR definition; connectionReferences may accompany either and lands in the same save. WHOLE definition: call get_live_flow, mutate properties.definition, pass it here. RENAME: pass displayName alone. Power Automate rejects a PATCH carrying no flow content, so this re-saves the unchanged definition — the maker portal does the same. definition.description is required, and must be brief — we append " #flowstudio-mcp" to it.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionReferences | object | – | Connection references map copied from get_live_flow. Direct-flow entries use { connectionName, id }. Solution-aware entries also include { connectionReferenceLogicalName, source } and must retain tho… |
| definition | object | – | 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 ob… |
| displayName | string | – | Display name for the flow. Required when creating. |
| dryRun | boolean | – | Preview only, on BOTH paths: with flowName, apply the change to the live definition and return the result + what changed; without flowName, return the flow that WOULD be created. Nothing is written e… |
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | – | Name (ID) of the flow to update. Omit or leave blank to create a new flow. |
| operations | array | – | SURGICAL EDIT of an existing flow (requires flowName; do not combine with definition). An ordered list applied to the LIVE definition. Each item = { op, path, value? }. path is an ARRAY of literal ke… |
No output schema declared.
No examples provided.
update_store_flow ~266
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| businessImpact | string | – | – |
| businessJustification | string | – | – |
| businessValue | string | – | – |
| critical | boolean | – | – |
| description | string | – | – |
| environmentName | string | yes | Name of the Power Platform environment. |
| flowName | string | yes | Name (ID) of the flow. |
| monitor | boolean | – | Enable/disable monitoring for this flow. |
| ownerBusinessUnit | string | – | – |
| ownerTeam | string | – | – |
| rule_notify_email | string | – | Comma-separated email addresses for notifications. |
| rule_notify_onfail | boolean | – | Send notification when the flow fails. |
| rule_notify_onmissingdays | number | – | Send notification when flow has not run for this many days (0 = disabled). |
| security | string | – | – |
| supportEmail | string | – | – |
| supportGroup | string | – | – |
| tags | string | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
What is the Power Automate MCP Server by Flow Studio server?
Power Automate MCP Server by Flow Studio is listed in the public MCP registry as io.github.ninihen1/flowstudio-mcp. Debug, build, and manage Power Automate cloud flows with AI agents. This page covers its hosted endpoint (https://mcp.flowstudio.app/mcp).
Is the Power Automate MCP Server by Flow Studio server safe to use?
Power Automate MCP Server by Flow Studio scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Power Automate MCP Server by Flow Studio server expose?
Power Automate MCP Server by Flow Studio exposes 29 tools: tool_search, list_skills, report_bug, list_store_flows, get_store_flow, and 24 more. Their descriptions and schemas cost roughly 5,424 tokens of context every time the server is loaded.
Does the Power Automate MCP Server by Flow Studio server require authentication?
Yes. Power Automate MCP Server by Flow Studio asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Power Automate MCP Server by Flow Studio server still maintained?
Power Automate MCP Server by Flow Studio is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.