Configure pa flow mcp

Skill Mr-M-tastic/Power-Automate-MCP/skills/configure-pa-flow-mcp

Configure the pa-flow MCP server for a Power Automate cloud flow. USE WHEN "configure flow", "set up Power Automate MCP", "connect to my flow", "pa-flow not working", "edit my cloud flow", "configure session". Extracts environmentId + flowId from the Designer URL, signs in (browser loopback), and pulls the flow locally.From its SKILL.md

Install

npx -y skills add Mr-M-tastic/Power-Automate-MCP --skill configure-pa-flow-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

Configure the pa-flow MCP Server

Connect your AI tool to a specific Power Automate cloud flow so you can read and edit it live.

Prerequisites

Node.js 18+ (node -v). The plugin runs dist/index.js; if it's missing, run npm install && npm run build in the plugin folder.
A Power Automate license and access to the flow you want to edit.
A browser for one-time sign-in.

Instructions

1. Ask for the flow URL

Ask the user:

What is the URL of your Power Automate flow?

Open the flow in your browser (Power Automate Designer or Solutions) and copy the address bar URL. It looks like: https://make.powerautomate.com/environments/<env>/flows/<flowId> or .../environments/<env>/solutions/~preferred/flows/<flowId>

2. Pick the assistant

Ask which assistant is in use: copilot, codex, or claude (defaults to copilot).

3. Configure the session

Call configure_session with { url, assistant }. It extracts environmentId and flowId. If the URL has no flow id, call list_flows and let the user choose.

4. Sign in and pull

Call sync_pull. The first call opens a browser loopback for sign-in (token is cached afterward). On success a working copy is written to .pa-flow/<flowId>.json and you get a summary (display name, state, triggers, actions).

5. Confirm

Report the flow name, state, trigger(s), and action list. The session is now ready for /edit-flow and /add-connector-action.

Troubleshooting

403 / no access — the signed-in account lacks rights to the flow or environment. Confirm the account and that the flow is shared with them.
Login loop — delete ~/.pa-flow-mcp-token.json and retry sync_pull.
Conditional Access blocks device code — this server uses interactive browser auth (loopback) precisely to avoid that. Make sure a browser can open.