Debug, build, and manage Power Automate cloud flows with AI agents
{
"mcpServers": {
"io-github-ninihen1-flowstudio-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Debug, build, and manage Power Automate cloud flows with AI agents
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 3 days ago. 8 stars.
Will it work with my client?
Transport: . Compatibility not confirmed.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.ninihen1/flowstudio-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.

You can click through the portal and find the root cause. Your agent can't — unless it has 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 | 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-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.
Inside a Codex session, install skil