Skip to content

Connect FlowStudio MCP with a browser key

Some organizations block the Microsoft permission prompt that FlowStudio MCP normally needs. A browser key gets you connected anyway. Instead of FlowStudio calling Power Automate on your behalf, your agent’s calls run through your own browser, inside the Power Automate session you are already signed in to. Your Power Automate token never leaves your browser, and there is nothing for an admin to approve.

The short version: Create a browser key on your dashboard, install the FlowStudio browser extension, paste the key into the extension to pair, and keep a Power Automate tab signed in. Your agent setup is identical to a regular key: same endpoint, same x-api-key header.

When to use a browser key

The regular setup is better when you can use it: connect the Power Automate and Power Apps permissions on your dashboard and generate a normal API key. It is faster per call and works with your browser closed.

Use a browser key when that permission prompt is the problem:

  • You click Connect next to Power Automate and Microsoft shows “approval required” or an error instead of the permission screen.
  • Your admin cannot or will not approve the FlowStudio permissions for your tenant.

Signing in to mcp.flowstudio.app itself is a separate, basic Microsoft sign-in. Tenants that block the Power Platform permissions usually still allow that, so you can reach your dashboard and create a browser key.

How it works

A browser key has no permissions of its own. When your agent makes a call with a browser key, the FlowStudio server hands the call to the FlowStudio extension in your browser. The extension runs it inside your signed-in Power Automate session and sends the result back. To Power Automate it looks like you clicking around the portal, because effectively it is.

Everything works over this path: listing environments and flows, reading run history and action outputs, and updating flow definitions.

Step 1: create a browser key

  1. Sign in at mcp.flowstudio.app/dashboard with your Microsoft account.
  2. Find the Browser keys card. Give the key a label, like “Work laptop”, and click Create key.
  3. Copy the key. It stays visible on your dashboard, so you can come back and copy it again later.

FlowStudio MCP dashboard Browser keys card with a newly created key (value redacted), its Rotate and Revoke buttons, and the Create key button

Figure: Create a browser key on the dashboard - the key stays visible so you can copy it again later

Step 2: install the browser extension

The extension is under review in the Chrome and Edge stores. Until it is published, install it manually. It takes about a minute.

Download the extension zip from the Install the browser extension card on your dashboard, then:

Chrome

  1. Unzip the download to a folder you will keep.
  2. Open chrome://extensions.
  3. Turn on Developer mode (top right).
  4. Click Load unpacked and choose the unzipped folder.

Chrome extensions page with Developer mode turned on and the Load unpacked button

Figure: Chrome - turn on Developer mode (top right), then click Load unpacked

Edge

  1. Unzip the download to a folder you will keep.
  2. Open edge://extensions.
  3. Turn on Developer mode (left sidebar).
  4. Click Load unpacked and choose the unzipped folder.

Keep the unzipped folder where it is. Deleting or moving it removes the extension. If your organization disables Developer mode, ask your admin to allow it, or to allowlist the extension once it is in the store.

Edge extensions page with the Developer mode toggle at the bottom of the left sidebar

Figure: Edge - turn on Developer mode (bottom of the left sidebar), then click Load unpacked

Step 3: pair your browser

  1. Pin the FlowStudio icon in your browser toolbar.
  2. Click the icon and paste your browser key into the popup.
  3. Open make.powerautomate.com and sign in. Keep this tab around; the extension works through it.

The key pairs with the first Microsoft account that uses it. If someone else tries to pair the same key, they are rejected. One key per person; create as many keys as you need.

FlowStudio browser extension popup showing Connected status while signed in to Power Automate

Figure: Paired and Connected - the extension works through your signed-in Power Automate tab

Step 4: connect your agent

Configure your agent exactly like a regular key: endpoint https://mcp.flowstudio.app/mcp, header x-api-key, value your browser key. Per-agent setup for Claude, Copilot, Codex, Cursor, and more is in Getting Started with FlowStudio MCP; only the key value changes.

Test it: ask your agent to “List my Power Platform environments” while your Power Automate tab is open.

What to expect

  • Calls are slower. Every call makes a round trip through your browser, which adds a second or two. Listing operations that page through many flows take noticeably longer than on a regular key.
  • Your browser has to be open. If the extension is not running or your Power Automate tab is signed out, calls fail immediately with a message telling you to reopen the tab. Nothing hangs; fix the tab and try again.
  • Calls count against your plan the same as with a regular key.

Rotate or revoke a key

Both are on the key’s row on the Browser keys card.

  • Rotate gives the key a new secret and keeps its label and pairing. Paste the new value into the extension popup on the paired browser and update it in your agent config; the old value stops working within about a minute.
  • Revoke kills the key. The paired browser stops working within about a minute.

Troubleshooting

  • “Open Power Automate in the browser running the FlowStudio extension”: your paired browser is not reachable. Open make.powerautomate.com in the browser with the extension, make sure you are signed in, and retry.
  • Empty environment list even though you have access: usually the same cause. Check the extension is paired and your Power Automate tab is signed in before concluding you have no access.
  • “key_bound_elsewhere”: this key already belongs to a different Microsoft account. Create your own key on your dashboard.
  • HTTP 401 or 403: the key is missing from the request or sent with the wrong header. The header must be x-api-key, not Authorization: Bearer.

Related guides