Flow Studio MCP — Browser Connect

Let an AI agent reach Power Automate through your own signed-in browser session — your token never leaves the browser.

Flow Studio MCP — Browser Connect lets an AI agent work with your Power Automate flows through your own signed-in Microsoft session — without the cloud ever holding your token. It's built for locked-down tenants. Many organisations can't (or won't) approve a hosted MCP server or grant it admin consent to reach Power Automate. This extension takes a different path: instead of the cloud storing a delegated token, it borrows the Power Automate session token that already exists in your browser and runs the agent's requests locally, on your machine, as you. Your token never leaves the browser — only the request specifications go out, and only the responses come back. HOW IT WORKS 1. Subscribe at mcp.flowstudio.app and create a browser-mode key in the dashboard. 2. Paste the key into this extension's popup ("Connect"). 3. Keep a Power Automate tab open (make.powerautomate.com) so the extension can pick up your session. 4. Point your AI agent's MCP client at your Flow Studio MCP server. When the agent asks to read or change a flow, the request is relayed to this browser, executed with your session, and the result is returned. WHAT THE AGENT CAN DO (through your session) • List environments, flows, and connections • Read and update flow definitions • Start, stop, trigger, cancel, and resubmit runs • Inspect run history and action-level inputs/outputs to debug failures …all scoped to exactly what YOU are permitted to do in Power Automate — nothing more. YOUR TOKEN NEVER LEAVES YOUR BROWSER This is the whole point. The extension reads your existing Power Automate token from the page and attaches it to Power Automate API calls locally. It is held in memory only, never written to disk, and never sent to Flow Studio or anywhere else. The only things that cross the network are the request to run (method, URL, headers, body) and Power Automate's response. Requests are hard-restricted to Microsoft Power Automate and Power Apps API hosts — a relayed request pointing anywhere else is refused. ONE KEY, ONE IDENTITY A key pairs to the Microsoft account it first runs as, so an agent always acts as a single, predictable identity. You can create a separate key per client or tenant and revoke any of them instantly from the dashboard. REQUIREMENTS • A Flow Studio MCP subscription and a browser-mode key (mcp.flowstudio.app). • You must be signed in to Power Automate in this browser. Flow Studio MCP is an independent product and is not affiliated with or endorsed by Microsoft. Power Automate, Power Apps, and Microsoft are trademarks of Microsoft Corporation. Learn more: https://mcp.flowstudio.app