Skip to main content
plugin

flow-studio-power-automate — Claude Code plugin

Connects Claude Code to Power Automate cloud flows via Flow Studio MCP. Helps inspect action payloads, loop iterations, and nested failures directly.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-plugins-community
/plugin install flow-studio-power-automate@claude-community
Open on GitHub

What flow-studio-power-automate does

Graph API only shows top-level run status. Action payloads, child flow errors, and loop steps remain hidden. This plugin bridges that gap via Flow Studio MCP: Claude Code gets direct access to input and output bodies, matching what developers see inside the Power Automate portal.

The plugin groups capabilities into five functional skills. The modules power-automate-mcp, power-automate-debug, and power-automate-build call live APIs to inspect, diagnose, and scaffold cloud flows. Monitoring and governance tools query a daily cached snapshot of tenant data instead.

Accessing the cached store requires a FlowStudio for Teams or MCP Pro+ subscription, and connecting the MCP server requires an API token from mcp.flowstudio.app.

What it helps with

  • inspect action-level inputs and outputs behind a failed cloud flow run
  • scan hundreds of loop iterations for corrupted data without clicking through portal runs
  • generate and deploy new Power Automate flow definitions from Claude Code
  • audit connectors and identify orphaned cloud flows across the tenant

Example prompts for the agent

  • Check the latest failed run of ProcessInvoices and inspect the input payload of the failing action
  • Scan all iterations of the main loop and find which ones produced empty outputs
  • Scaffold a new Power Automate cloud flow definition to send notifications when an item is created

How to install flow-studio-power-automate

Plugin marketplace

/plugin marketplace add anthropics/claude-plugins-community
/plugin install flow-studio-power-automate@claude-community

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about flow-studio-power-automate

How to install flow-studio-power-automate in Claude Code?

Run /plugin marketplace add anthropics/claude-plugins-community followed by /plugin install flow-studio-power-automate@claude-community.

What does flow-studio-power-automate do?

It gives Claude Code action-level visibility into Power Automate runs, allowing the agent to read action inputs, inspect outputs, and diagnose nested child flow failures.

What subscriptions or credentials are required?

Connecting the MCP server requires an API key from mcp.flowstudio.app, while cached store features for monitoring and governance require a FlowStudio for Teams or MCP Pro+ plan.

Source text

SKILL.md · MIT
# FlowStudio MCP — Power Automate Skills for AI Agents

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. FlowStudio MCP exposes all of it.

![Agent debugging a Power Automate flow via MCP](assets/demo-debug.gif)

**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](assets/portal-vs-reality.png)

![With FlowStudio MCP, the agent sees what you see](assets/mcp-root-cause.png)

## When you need this

- Your agent can see that a flow failed, but not why — Graph API only returns status codes
- You want your agent to see action-level inputs and outputs, like you can in the portal
- A loop has hundreds of iterations and some produced bad output — in the portal you'd click through each one, but the agent can scan all iteration inputs and outputs at once
- You want to check flow health, failure rates, and maker activity across your tenant without opening the admin center
- You need to classify flows, detect orphaned resources, or audit connectors at scale — without installing the CoE Starter Kit
- You're tired of being the middle-man between your agent and the portal

## Graph API vs FlowStudio MCP

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 | FlowStudio 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**         |

## Skills

| Skill                                                            | Description                                                                                                    |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [`power-automate-mcp`](skills/power-automate-mcp/)               | Connect to and operate Power Automate cloud flows — list flows, read definitions, check runs, resubmit, cancel |
| [`power-automate-debug`](skills/power-automate-debug/)           | Step-by-step diagnostic process for investigating failing flows                                                |
| [`power-automate-build`](skills/power-automate-build/)           | Build, scaffold, and deploy Power Automate flow definitions from scratch                                       |
| [`power-automate-monitoring`](skills/power-automate-monitoring/) | Flow health, failure rates, maker inventory, Power Apps, environment and connection counts                     |
| [`power-automate-governance`](skills/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](https://agentskills.io/specification)
and works with any compatible agent.

### Supported agents

Copilot, Claude Code, ChatGPT, Codex, OpenClaw, Gemini CLI, Cursor, Goose, Amp, OpenHands

## Guides

Full walkthroughs on [learn.flowstudio.app](https://learn.flowstudio.app):

- [Getting started](https://learn.flowstudio.app/mcp-getting-started) — install FlowStudio MCP for any agent
- [Build flows with AI agents](https://learn.flowstudio.app/build-power-automate-flows-with-ai-agents) — a worked 3-step example
- [Vibe code Power Automate](https://learn.flowstudio.app/vibe-code-power-automate) — describe the flow, the agent builds it
- [Power Automate in VS Code](https://learn.flowstudio.app/power-automate-ide) — work on flows from your editor
- [Debug a failing flow](https://learn.flowstudio.app/mcp-debug) — find the root cause from action-level data
- By agent: [ChatGPT](https://learn.flowstudio.app/chatgpt-power-automate) · [Claude](https://learn.flowstudio.app/claude-power-automate) · [GitHub Copilot](https://learn.flowstudio.app/github-copilot-power-automate) · [Copilot Studio](https://learn.flowstudio.app/copilot-studio-power-automate) · [Codex](https://learn.flowstudio.app/codex-power-automate)

## Quick Start

### Connect from ChatGPT or claude.ai

Sign in with your Microsoft account instead of pasting a key. Add
`https://mcp.flowstudio.app/mcp/oauth` as a connector in ChatGPT (Developer mode
on) or at claude.ai, then follow the sign-in prompt. Walkthrough:
[ChatGPT for Power Automate](https://learn.flowstudio.app/chatgpt-power-automate).

### Install as Claude Code plugin

Available through the Claude plugin marketplace after approval. To test locally:

```bash
git clone https://github.com/ninihen1/power-automate-mcp-skills.git
claude --plugin-dir ./power-automate-mcp-skills
```

Then connect the MCP server:

```bash
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
  --header "x-api-key: <YOUR_TOKEN>"
```

Get your token at [mcp.flowstudio.app](https://mcp.flowstudio.app).

### Install in Codex

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-governance
```

Then connect the MCP server in `~/.codex/config.toml`:

```toml
[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"

[mcp_servers.flowstudio.http_headers]
x-api-key = "<YOUR_TOKEN>"
```

### Install via skills.sh

Search for [flowstudio on skills.sh](https://skills.sh/?q=flowstudio), or:

```bash
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-governance
```

### Install via ClawHub

```bash
npx clawhub@latest install power-automate-mcp
```

### Install via Smithery

```bash
npx smithery skill add flowstudio/power-automate-mcp
```

### Manual install

Copy the skill folder(s) into your project's `.github/skills/` directory
(or wherever your agent discovers skills).

### Connect the MCP server

**Claude Code:**

```bash
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
  --header "x-api-key: <YOUR_TOKEN>"
```

**Codex** (`~/.codex/config.toml`):

```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`):

```json
{
  "servers": {
    "flowstudio": {
      "type": "http",
      "url": "https://mcp.flowstudio.app/mcp",
      "headers": { "x-api-key": "<YOUR_TOKEN>" }
    }
  }
}
```

Get your token at [mcp.flowstudio.app](https://mcp.flowstudio.app).

## Real debugging examples

These are from real production investigations, not demos.

- **[Expression error in child flow](examples/fix-expression-error.md)** —
  `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.

- **[Data entry, not a flow bug](examples/data-not-flow.md)** —
  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.

- **[Null value crashes child flow](examples/null-child-flow.md)** —
  `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`.

## Prerequisites

- A [FlowStudio](https://mcp.flowstudio.app) MCP subscription (all live tools)
- For store tools (monitoring, governance): FlowStudio for Teams or MCP Pro+
- MCP endpoint: `https://mcp.flowstudio.app/mcp`
- API key / JWT token (passed as `x-api-key` header)

## Repository structure

```
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                        MIT
```

## Available on GitHub

Works with Copilot, Claude, ChatGPT, and any MCP-compatible agent.

- [awesome-copilot](https://github.com/github/awesome-copilot) (merged)
- [skills.sh](https://skills.sh/?q=flowstudio) (3K+ installs)
- [Smithery](https://smithery.ai/skills/flowstudio/power-automate-mcp) (published)
- [ClawHub](https://clawhub.ai) (v1.1.0)

## Contributing

Contributions welcome. Each skill folder must contain a `SKILL.md` with the
required frontmatter. See the existing skills for the format.

## License

[MIT](LICENSE)

---

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

© ninihen1 · MIT · ninihen1/power-automate-mcp-skills

Similar plugins

All plugins for Automation and no-code: n8n, Zapier, Make →

From the same set2

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor