/flowstudio-power-automate-mcp

name: flowstudio-power-automate-mcp
description: >-
  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
  `flowstudio-power-automate-build`, `flowstudio-power-automate-debug`, `flowstudio-power-automate-monitoring`
  (Pro+), or `flowstudio-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

Power Automate via FlowStudio MCP — Foundation

This skill is the **plumbing layer**. It gives an AI agent a reliable way to talk to a FlowStudio MCP server, discover what tools are available, and handle the responses cleanly. The actual workflow narratives live in four specialized skills that all build on this one.

> **Real debugging examples**: [Expression error in child flow](https://github.com/ninihen1/power-automate-mcp-skills/blob/main/examples/fix-expression-error.md) | > [Data entry, not a flow bug](https://github.com/ninihen1/power-automate-mcp-skills/blob/main/examples/data-not-flow.md) | > [Null value crashes child flow](https://github.com/ninihen1/power-automate-mcp-skills/blob/main/examples/null-child-flow.md)

> **Requires:** A [FlowStudio](https://mcp.flowstudio.app) MCP subscription (or > compatible Power Automate MCP server). You will need: > - MCP endpoint: `https://mcp.flowstudio.app/mcp` (same for all subscribers) > - API key / JWT token (`x-api-key` header — NOT Bearer) > - In ChatGPT or claude.ai there is no key: add `https://mcp.flowstudio.app/mcp/oauth` > as a connector and sign in with Microsoft — see the > [ChatGPT walkthrough](https://learn.flowstudio.app/chatgpt-power-automate) > - Power Platform environment name (e.g. `Default-<tenant-guid>`)

---

Which Skill to Use When

Skills are organized by **use-case intent**, not by which tools they call. Multiple skills reuse the same underlying tools — pick by what the user is trying to accomplish.

| The user wants to… | Load this skill | |---|---| | Make or change a flow (build new, modify existing, fix a bug, deploy) | **`flowstudio-power-automate-build`** | | Diagnose why a flow failed (root cause analysis on a failing run) | **`flowstudio-power-automate-debug`** | | See tenant-wide flow health, failure rates, asset inventory | **`flowstudio-power-automate-monitoring`** *(Pro+)* | | Tag, audit, classify, score, or offboard flows | **`flowstudio-power-automate-governance`** *(Pro+)* | | Just connect, set up auth, write the helper, parse responses | this skill (foundation) |

**Same tools, different lenses.** `flowstudio-power-automate-build` and `flowstudio-power-automate-debug` both call `update_live_flow`, `get_live_flow`, and the run-error tools — they differ in *direction* (forward vs backward) and *intent* (compose vs diagnose). `flowstudio-power-automate-monitoring` and `flowstudio-power-automate-governance` both call the Store tools — they differ in *audience* (ops vs compliance) and *outcome* (read health vs write metadata). Don't try to memorize "which tools belong to which skill"; pick the skill by what the user is doing.

---

Source of Truth

| Priority | Source | Covers | |----------|--------|--------| | 1 | **Real API response** | Always trust what the server actually returns | | 2 | **`tool_search` / `list_skills`** | Authoritative tool schemas, parameter names, types, required flags | | 3 | **SKILL docs & reference files** | Workflow narrative, response shapes, non-obvious behaviors |

If documentation disagrees with a real API response, the API wins. Tool schemas in this skill (or any other) may lag the server — call `tool_search` to confirm the current shape before invoking a tool you haven't used recently.

---

How Agents Discover Tools

The FlowStudio MCP server (v1.1.5+) exposes two **non-billable** meta-tools that let an agent load only the tools relevant to the current task. Use these in preference to `tools/list` (which loads all 30+ schemas at once) or guessing tool names.

| Meta-tool | When to call | |---|---| | `list_skills` | Cold start — see the available bundles (`build-flow`, `create-flow`, `debug-flow`, `monitor-flow`, `discover`, `governance`) and pick one | | `tool_search` with `query: "skill:<name>"` | Load the full schema set for one bundle (e.g. `skill:debug-flow`) | | `tool_search` with `query: "select:tool1,tool2"` | Load specific tools by name (e.g. when chaining across bundles) | | `tool_search` with `query: "<keywords>"` | Free-text search when the user request is ambiguous (e.g. `"cancel run"`) |

The server's `tool_search` bundles are intentionally **narrower than this skill family** — they're starter packs of the most-likely-needed tools per intent. A workflow skill (e.g. `flowstudio-power-automate-debug`) may pull a bundle and then call `tool_search` again for additional tools as the workflow progresses.

# Cold start — pick a bundle by intent
skills = mcp("list_skills", {})
# [{"name": "debug-flow", "description": "Investigate why a flow is failing...",
#   "tools": ["get_live_flow_runs", "get_live_flow_run_error", ...]}, ...]

# Load schemas for the bundle
debug_tools = mcp("tool_search", {"query": "skill:debug-flow"})

Current common bundles:

| Bundle | Use when | |---|---| | `create-flow` | Creating a brand-new flow; includes environment/connection discovery, connector description, dynamic options, and `update_live_flow` | | `build-flow` | Reading or modifying an existing flow definition | | `debug-flow` | Investigating failed runs and action-level inputs/outputs | | `monitor-flow` | Starting/stopping, triggering, cancelling, or resubmitting runs | | `discover` | Enumerating environments, flows, and connections | | `governan