# Power Automate MCP Server by Flow Studio

Lets your agent inspect Power Automate cloud flows down to action inputs and loop iterations. Useful when a run fails and Graph API shows only the status code.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 34
- Author: ninihen1
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ninihen1/power-automate-mcp-skills
- Updated: 2026-09-04
- HTML: https://affpapa.org/en/nevibecode/mcp/power-automate-mcp-server-by-flow-studio

## What it does

Graph API hands an agent a run status and stops there. This server passes through what the portal shows a human: what each action received, what it returned, which loop iterations went wrong, what happened inside a child flow. Flow definitions come back as full JSON and can be written back. Runs can be resubmitted or cancelled.

The server is remote and speaks HTTP at `https://mcp.flowstudio.app/mcp`. You need a token from `mcp.flowstudio.app`, sent in the `x-api-key` header. No token, no connection.

Five skills ship in the repo: operate flows, diagnose failures, build definitions, watch health, handle governance. The first three call the live API. Monitoring and governance read a daily snapshot and need a FlowStudio for Teams or MCP Pro+ subscription.

## Requirements
- Remote server: `https://mcp.flowstudio.app/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http power-automate-mcp-server-by-flow-studio https://mcp.flowstudio.app/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add power-automate-mcp-server-by-flow-studio --url https://mcp.flowstudio.app/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "power-automate-mcp-server-by-flow-studio": {
            "url": "https://mcp.flowstudio.app/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "power-automate-mcp-server-by-flow-studio": {
            "type": "http",
            "url": "https://mcp.flowstudio.app/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http power-automate-mcp-server-by-flow-studio https://mcp.flowstudio.app/mcp
```

## When to use it
- trace a failed run back to the exact action that broke
- scan every loop iteration for bad output in one pass
- scaffold a new flow definition and deploy it from the agent
- resubmit a failed run or cancel a stuck one
- check flow health and maker activity across a tenant

## Example prompts
- Show me what the “Send an email” action received in the last failed run
- Scaffold a flow that copies SharePoint items to Excel and show me the JSON before deploying
- Find the iterations in this loop where the output differs from what I expect

## Similar
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89433
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [AIHawk](https://affpapa.org/en/nevibecode/mcp/aihawk.md) — MCP server · ★ 32221
- [Skyvern](https://affpapa.org/en/nevibecode/mcp/skyvern.md) — MCP server · ★ 23263
- [SeleniumBase MCP](https://affpapa.org/en/nevibecode/mcp/seleniumbase-mcp.md) — MCP server · ★ 13169
- [Inbox Zero](https://affpapa.org/en/nevibecode/mcp/inbox-zero.md) — MCP server · ★ 12791

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md