By ninihen1
Manage Power Automate cloud flows from the command line: build and deploy flow definitions, debug failures with action-level diagnostics, monitor tenant-wide run health and compliance, and govern flows with classification, orphan detection, and connector auditing.
Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from scratch. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app
Debug failing Power Automate cloud flows using the FlowStudio MCP server. The Graph API only shows top-level status codes. This skill gives your agent action-level inputs and outputs to find the actual root cause. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app
Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app
Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills` / `tool_search`, and oversized-response handling. Load this skill first when connecting an agent to Power Automate. For specialized workflows, load `power-automate-build`, `power-automate-debug`, `power-automate-monitoring` (Pro+), or `power-automate-governance` (Pro+) — each contains the workflow narrative, this skill provides the plumbing they all rely on. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app
Pro+ subscription required. Tenant-wide Power Automate monitoring using the FlowStudio MCP cached store: failure rates, run-health trends, maker/app inventory, inactive owners, and compliance/health reports. Use only for aggregated tenant views. For one environment, one flow, run control, or root-cause debugging, use power-automate-mcp, power-automate-debug, or the server monitor-flow bundle. Requires FlowStudio for Teams or MCP Pro+.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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 skills directly:
npx claudepluginhub ninihen1/power-automate-mcp-skillsConsul - Enterprise Microsoft ecosystem orchestrator for TVS (Trusted Virtual Solutions) multi-entity multi-tenant deployment. 19 agents, 18 commands, 17 skills, 14 hooks, 5 workflows. MCP server for Graph API, Dataverse, Fabric, and Planner.
Expert skills for designing, building, and deploying Make.com automation scenarios — for Claude Code and other AI agents
Design complex n8n workflows with AI assistance - loops, branching, error handling
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques and MCP tools integration.\n\nExamples:\n- <example>\n Context: User wants to create a Slack notification workflow when a new GitHub issue is created.\n user: "I need to create an n8n workflow that sends a Slack message whenever a new GitHub issue is opened"\n assistant: "I'll use the n8n-workflow-builder agent to design and build this GitHub-to-Slack automation workflow with proper validation."\n <commentary>\n The user needs n8n workflow creation, so use the n8n-workflow-builder agent to handle the complete workflow design, validation, and deployment process.\n </commentary>\n</example>\n- <example>\n Context: User has an existing n8n workflow that needs debugging and optimization.\n user: "My n8n workflow keeps failing at the HTTP Request node, can you help me fix it?"\n assistant: "I'll use the n8n-workflow-builder agent to analyze and debug your workflow, focusing on the HTTP Request node configuration."\n <commentary>\n Since this involves n8n workflow troubleshooting and validation, use the n8n-workflow-builder agent to diagnose and fix the issue.\n </commentary>\n</example>\n- <example>\n Context: User wants to understand n8n best practices and available nodes for a specific use case.\n user: "What are the best n8n nodes for processing CSV data and sending email reports?"\n assistant: "I'll use the n8n-workflow-builder agent to explore the available nodes and recommend the best approach for CSV processing and email automation."\n <commentary>\n This requires n8n expertise and node discovery, so use the n8n-workflow-builder agent to provide comprehensive guidance.\n </commentary>\n</example>
Production-grade n8n workflow building skills. Pairs with the official n8n instance-level MCP server to teach Claude how to architect, validate, and ship workflows that work in production.
Prefect workflow orchestration - read-only MCP server for diagnostics, CLI skill for mutations