Flowstudio-Power-Automate-Mcp

# 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)

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