Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-ninihen1-flowstudio-mcp": {
"args": [
"-y",
"skills"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'skills' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked skills against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
Enhanced MCP server for GitLab: group projects listing and activity tracking
Yunxiao MCP Server provides AI assistants with the ability to interact with the Yunxiao platform. It provides a set of tools that interact with Yunxiao's API, allowing AI assistants to manage Codeup repository, Project, Pipeline, Packages etc.
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
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 metad