Power Automate MCP Server by Flow Studio

warnings

mcp.flowstudio.app

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

https://mcp.flowstudio.app/mcpWebsiteOAuthMCP 2025-03-26v1.2.70last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 426 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

claude mcp add --transport http power-automate-mcp-server-by-flow-studio https://mcp.flowstudio.app/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://mcp.flowstudio.app/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://mcp.flowstudio.app/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "power-automate-mcp-server-by-flow-studio": {
      "url": "https://mcp.flowstudio.app/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

{
  "servers": {
    "power-automate-mcp-server-by-flow-studio": {
      "type": "http",
      "url": "https://mcp.flowstudio.app/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://mcp.flowstudio.app
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 34 tools listable
Credentials demanded in prose	✕get_store_maker, update_live_flow, list_live_flows These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

3 of the 34 tools listed anonymously say in their own descriptions that they need an account or a key (get_store_maker, update_live_flow, list_live_flows), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

34 tools usable without signing in

The server exposes a public surface before authorization: tool_search, list_skills, report_bug, 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.

Tools

add_live_flow_to_solutioncancel_live_flow_rundescribe_live_connectorget_live_dynamic_optionsget_live_dynamic_propertiesget_live_flowget_live_flow_http_schemaget_live_flow_run_action_outputsget_live_flow_run_errorget_live_flow_runsget_live_flow_trigger_urlget_store_flowget_store_flow_errorsget_store_flow_runsget_store_flow_summaryget_store_flow_trigger_urlget_store_makerlist_live_connectionslist_live_environmentslist_live_flowslist_skillslist_store_connectionslist_store_environmentslist_store_flowslist_store_makerslist_store_power_appsreport_bugresubmit_live_flow_runset_live_flow_stateset_store_flow_statetool_searchtrigger_live_flowupdate_live_flowupdate_store_flow

Contract history

2 Sep 2026v1.2.70first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/power-automate-mcp-server-by-flow-studio/badge.svg)](https://mcpi.app/servers/power-automate-mcp-server-by-flow-studio)