Power Automate MCP Server by Flow Studio

Registre officiel Outils de développement

Debug, build, and manage Power Automate cloud flows with AI agents

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http power-automate-mcp-server-by-flow-studio 'https://mcp.flowstudio.app/mcp' --header 'x-api-key: <Flow Studio MCP API key (get one at https://mcp.flowstudio.app)>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "power-automate-mcp-server-by-flow-studio": {
            "type": "http",
            "url": "https://mcp.flowstudio.app/mcp",
            "headers": {
                "x-api-key": "<Flow Studio MCP API key (get one at https://mcp.flowstudio.app)>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. FlowStudio MCP — Power Automate Skills for AI Agents
  2. When you need this
  3. Graph API vs FlowStudio MCP
  4. Skills
  5. Guides
  6. Quick Start
  7. Real debugging examples
  8. Prerequisites
  9. Repository structure
  10. Available on GitHub
  11. Contributing
  12. License

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.

You can click through the portal and find the root cause. Your agent can't — unless it has MCP.

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 seesGraph APIFlowStudio MCP
Run passed or failedYesYes
Action inputs and outputsNoYes
Error details beyond status codeNoYes
Child flow run detailsNoYes
Loop iteration dataNoYes
Flow definition (read + write)LimitedFull JSON
Resubmit / cancel runsLimitedYes
Cached flow health & failure ratesNoYes
Maker / Power Apps / connection inventoryNoYes
Governance metadata (tags, impact, owner)NoYes

Skills

SkillDescription
power-automate-mcpConnect to and operate Power Automate cloud flows — list flows, read definitions, check runs, resubmit, cancel
power-automate-debugStep-by-step diagnostic process for investigating failing flows
power-automate-buildBuild, scaffold, and deploy Power Automate flow definitions from scratch
power-automate-monitoringFlow health, failure rates, maker inventory, Power Apps, environment and connection counts
power-automate-governanceClassify 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.

Supported agents

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

Guides

Full walkthroughs on learn.flowstudio.app:

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.

Install as Claude Code plugin

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-skills

Then 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.

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:

[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, 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-governance
Install via ClawHub
npx clawhub@latest install power-automate-mcp
Install via Smithery
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:

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.

Real debugging examples

These are from real production investigations, not demos.

  • Expression error in child flow — 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 — 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 — 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 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.

Contributing

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

License

MIT


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

Questions fréquentes

Qu'est-ce que Power Automate MCP Server by Flow Studio ?

Debug, build, and manage Power Automate cloud flows with AI agents

Comment installer Power Automate MCP Server by Flow Studio ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http power-automate-mcp-server-by-flow-studio 'https://mcp.flowstudio.app/mcp' --header 'x-api-key: <Flow Studio MCP API key (get one at https://mcp.flowstudio.app)>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Power Automate MCP Server by Flow Studio ?

Oui. Il attend x-api-key, à renseigner dans sa configuration.

Power Automate MCP Server by Flow Studio est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Power Automate MCP Server by Flow Studio ?

Il est publié par ninihen1. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.