cursor-plugin — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cursor-plugin (MCP Server) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Give your AI agent the same visibility you have in the Power Automate portal — plus a bit more. The Graph API only returns top-level run status — agents can't see action inputs, loop iterations, or nested failures. Flow Studio MCP exposes all of it.
Agent debugging a Power Automate flow via MCP
You can click through the portal and find the root cause. Your agent can't — unless it has MCP.
The portal shows everything to a human — but agents only see the top-level error via Graph API
With Flow Studio MCP, the agent sees what you see
The core difference: Graph API gives your agent run status. MCP gives your agent the inputs and outputs of every action.
| What the agent sees | Graph API | Flow Studio MCP |
|---|---|---|
| Run passed or failed | Yes | Yes |
| Action inputs and outputs | No | Yes |
| Error details beyond status code | No | Yes |
| Child flow run details | No | Yes |
| Loop iteration data | No | Yes |
| Flow definition (read + write) | Limited | Full JSON |
| Resubmit / cancel runs | Limited | Yes |
| Cached flow health & failure rates | No | Yes |
| Maker / Power Apps / connection inventory | No | Yes |
| Governance metadata (tags, impact, owner) | No | Yes |
| Skill | Description |
|---|---|
power-automate-mcp | Connect to and operate Power Automate cloud flows — list flows, read definitions, check runs, resubmit, cancel |
power-automate-debug | Step-by-step diagnostic process for investigating failing flows |
power-automate-build | Build, scaffold, and deploy Power Automate flow definitions from scratch |
power-automate-monitoring | Flow health, failure rates, maker inventory, Power Apps, environment and connection counts |
power-automate-governance | Classify flows by impact, detect orphans, audit connectors, manage notifications, compute archive scores |
The first three skills use live Power Automate API calls. The monitoring and governance skills use the cached store — a daily snapshot with aggregated stats, remediation hints, and governance metadata. Requires a FlowStudio for Teams or MCP Pro+ subscription for store tools.
Each skill follows the Agent Skills specification and works with any compatible agent.
Copilot, Claude Code, Codex, OpenClaw, Gemini CLI, Cursor, Goose, Amp, OpenHands
Available through the Claude plugin marketplace after approval. To test locally:
git clone https://github.com/ninihen1/power-automate-mcp-skills.git
claude --plugin-dir ./power-automate-mcp-skillsThen connect the MCP server:
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
--header "x-api-key: <YOUR_TOKEN>"Get your token at mcp.flowstudio.app.
Inside a Codex session, install skills directly:
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-mcp
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-debug
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-build
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-monitoring
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-governanceThen connect the MCP server in ~/.codex/config.toml:
[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"
[mcp_servers.flowstudio.http_headers]
x-api-key = "<YOUR_TOKEN>"Search for flowstudio on skills.sh, or:
npx skills add github/awesome-copilot -s flowstudio-power-automate-mcp
npx skills add github/awesome-copilot -s flowstudio-power-automate-debug
npx skills add github/awesome-copilot -s flowstudio-power-automate-build
npx skills add github/awesome-copilot -s flowstudio-power-automate-monitoring
npx skills add github/awesome-copilot -s flowstudio-power-automate-governancenpx clawhub@latest install power-automate-mcpnpx smithery skill add flowstudio/power-automate-mcpCopy the skill folder(s) into your project's .github/skills/ directory (or wherever your agent discovers skills).
Claude Code:
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
--header "x-api-key: <YOUR_TOKEN>"Codex (~/.codex/config.toml):
[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"
[mcp_servers.flowstudio.http_headers]
x-api-key = "<YOUR_TOKEN>"Copilot / VS Code (.vscode/mcp.json):
{
"servers": {
"flowstudio": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp",
"headers": { "x-api-key": "<YOUR_TOKEN>" }
}
}
}Get your token at mcp.flowstudio.app.
These are from real production investigations, not demos.
contains(string(...)) crashed on a nested property. Agent traced through parent flow, into child, through loop iterations, and found the failing input. Portal showed "ExpressionEvaluationFailed" with no context.
User reported two "bugs" back to back. Agent proved both were data entry errors (missing comma in email, single address in CC field). Flow was correct. Diagnosed in seconds.
split(Name, ', ') crashed when 38% of records had null Names. Agent traced parent to child to loop to action, found the root cause, and deployed a fix via update_live_flow.
https://mcp.flowstudio.app/mcpx-api-key header)skills/
power-automate-mcp/ core connection & operation skill
power-automate-debug/ debug workflow skill
power-automate-build/ build & deploy skill
power-automate-monitoring/ flow health & tenant inventory skill
power-automate-governance/ compliance & governance skill
examples/ real debugging walkthroughs
README.md
LICENSE MITWorks with Copilot, Claude, and any MCP-compatible agent.
Contributions welcome. Each skill folder must contain a SKILL.md with the required frontmatter. See the existing skills for the format.
Keywords: Power Automate debugging, flow run history, expression evaluation failed, child flow failure, nested action errors, loop iteration output, agent automation MCP, Power Platform AI, flow definition deploy, resubmit failed run, flow monitoring, governance, CoE, orphan detection, connector audit, archive score, maker inventory
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.