Power Automate MCP
LeoYeAI/openclaw-master-skills
Connect to and operate Power Automate cloud flows via a FlowStudio MCP server.
Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via listskills / toolsearch, and oversized-response handling.
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/flowstudio-power-automate-mcp .claude/skills/flowstudio-power-automate-mcp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "flowstudio-power-automate-mcp" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcp into .claude/skills/flowstudio-power-automate-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flowstudio-power-automate-mcp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/flowstudio-power-automate-mcp .agents/skills/flowstudio-power-automate-mcp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flowstudio-power-automate-mcp" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcp into .agents/skills/flowstudio-power-automate-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flowstudio-power-automate-mcp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/flowstudio-power-automate-mcp .cursor/skills/flowstudio-power-automate-mcp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "flowstudio-power-automate-mcp" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcp into .cursor/skills/flowstudio-power-automate-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flowstudio-power-automate-mcp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/flowstudio-power-automate-mcp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/flowstudio-power-automate-mcp .gemini/skills/flowstudio-power-automate-mcp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "flowstudio-power-automate-mcp" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcp into .gemini/skills/flowstudio-power-automate-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flowstudio-power-automate-mcp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/flowstudio-power-automate-mcp .github/skills/flowstudio-power-automate-mcp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "flowstudio-power-automate-mcp" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcp into .github/skills/flowstudio-power-automate-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flowstudio-power-automate-mcp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/flowstudio-power-automate-mcp .opencode/skills/flowstudio-power-automate-mcp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "flowstudio-power-automate-mcp" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-mcp into .opencode/skills/flowstudio-power-automate-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flowstudio-power-automate-mcp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
flowstudio-power-automate-mcpFoundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via listskills / toolsearch, and oversized-response handling.
Flowstudio Power Automate MCP is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via listskills / toolsearch, 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…
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/MCP-BOOTSTRAP.md`, `references/action-types.md` and `references/connection-references.md`).
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol, Power Automate, Python and Node.js. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pipFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
mcp.flowstudio.appAlso links to:
github.comlearn.flowstudio.appFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Flowstudio Power Automate MCP loads about 3.4k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 168 tokens; SKILL.md has 1,192 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,192 words, ~3,429 tokens.
.claude/skills/flowstudio-power-automate-mcp/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.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 | Data entry, not a flow bug | Null value crashes child flow
Requires: A FlowStudio 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-keyheader — NOT Bearer)- In ChatGPT or claude.ai there is no key: add
https://mcp.flowstudio.app/mcp/oauthas a connector and sign in with Microsoft — see the ChatGPT walkthrough- Power Platform environment name (e.g.
Default-<tenant-guid>)
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.
| 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.
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 |
governance | Pro+ cached-store tagging, maker audit, and metadata updates |
All examples in this skill family use Python with urllib.request
(stdlib — no pip install needed). Node.js is an equally valid choice:
fetch is built-in from Node 18+, JSON handling is native, and async/await
maps cleanly onto the request-response pattern of MCP tool calls — making it
a natural fit for teams already working in a JavaScript/TypeScript stack.
| Language | Verdict | Notes |
|---|---|---|
| Python | Recommended | Clean JSON handling, no escaping issues, all skill examples use it |
| Node.js (≥ 18) | Recommended | Native fetch + JSON.stringify/JSON.parse; no extra packages |
| PowerShell | Avoid for flow operations | ConvertTo-Json -Depth silently truncates nested definitions; quoting and escaping break complex payloads. Acceptable for a quick connectivity smoke-test but not for building or updating flows. |
| cURL / Bash | Possible but fragile | Shell-escaping nested JSON is error-prone; no native JSON parser |
TL;DR — use the Core MCP Helper (Python or Node.js) below. Both handle JSON-RPC framing, auth, and response parsing in a single reusable function.
Use this helper throughout all subsequent operations:
import json, urllib.request
TOKEN = "<YOUR_JWT_TOKEN>"
MCP = "https://mcp.flowstudio.app/mcp"
def mcp(tool, args, cid=1):
payload = {"jsonrpc": "2.0", "method": "tools/call", "id": cid,
"params": {"name": tool, "arguments": args}}
req = urllib.request.Request(MCP, data=json.dumps(payload).encode(),
headers={"x-api-key": TOKEN, "Content-Type": "application/json",
"User-Agent": "FlowStudio-MCP/1.0"})
try:
resp = urllib.request.urlopen(req, timeout=120)
except urllib.error.HTTPError as e:
body = e.read().decode("utf-8", errors="replace")
raise RuntimeError(f"MCP HTTP {e.code}: {body[:200]}") from e
raw = json.loads(resp.read())
if "error" in raw:
raise RuntimeError(f"MCP error: {json.dumps(raw['error'])}")
text = raw["result"]["content"][0]["text"]
return json.loads(text)Common auth errors:
- HTTP 401/403 → token is missing, expired, or malformed. Get a fresh JWT from mcp.flowstudio.app.
- HTTP 400 → malformed JSON-RPC payload. Check
Content-Type: application/jsonand body structure.MCP error: {"code": -32602, ...}→ wrong or missing tool arguments. Calltool_searchwithselect:<toolname>to confirm the schema.
Equivalent helper for Node.js 18+ (built-in fetch — no packages required):
const TOKEN = "<YOUR_JWT_TOKEN>";
const MCP = "https://mcp.flowstudio.app/mcp";
async function mcp(tool, args, cid = 1) {
const payload = {
jsonrpc: "2.0",
method: "tools/call",
id: cid,
params: { name: tool, arguments: args },
};
const res = await fetch(MCP, {
method: "POST",
headers: {
"x-api-key": TOKEN,
"Content-Type": "application/json",
"User-Agent": "FlowStudio-MCP/1.0",
},
body: JSON.stringify(payload),
});
if (!res.ok) {
const body = await res.text();
throw new Error(`MCP HTTP ${res.status}: ${body.slice(0, 200)}`);
}
const raw = await res.json();
if (raw.error) throw new Error(`MCP error: ${JSON.stringify(raw.error)}`);
return JSON.parse(raw.result.content[0].text);
}Requires Node.js 18+. For older Node, replace
fetchwithhttps.requestfrom the stdlib or installnode-fetch.
A 3-line smoke test that confirms the token, endpoint, and helper all work:
skills = mcp("list_skills", {})
print(f"Connected — {len(skills)} skill bundles available:",
[s["name"] for s in skills])Expected output:
Connected — 6 skill bundles available: ['build-flow', 'create-flow', 'debug-flow', 'monitor-flow', 'discover', 'governance']If this fails, see the Common auth errors note above. If it succeeds, hand off to the workflow skill matching the user's intent.
Some MCP tool responses are large enough to overflow the agent's context window:
| Tool | Typical size | Cause |
|---|---|---|
describe_live_connector | 100-600 KB | Full Swagger spec for a connector |
get_live_dynamic_properties | 50-500 KB | Dynamic connector field schemas such as SharePoint list columns |
get_live_flow_run_action_outputs (no actionName) | 50 KB – several MB | Top-level action outputs; with an action in a foreach, every repetition can be returned |
get_live_flow (large flows) | 50-500 KB | Deeply nested branches |
list_live_flows (large tenants) | 50-200 KB | Hundreds of flow records |
Agent harnesses (Claude Code, VS Code Copilot, etc.) save oversized responses
to a temp file (e.g. tool-results/mcp-flowstudio-describe_live_connector-NNNN.txt)
and return the path instead of the inline JSON. The file is double-wrapped —
the outer MCP envelope plus the inner JSON-escaped payload:
[{"type":"text","text":"<JSON-escaped payload>"}]Two parses to reach a usable object:
import json
with open(path) as f:
raw = json.loads(f.read())
payload = json.loads(raw[0]["text"])$payload = ((Get-Content $path -Raw | ConvertFrom-Json)[0].text) | ConvertFrom-JsonoperationId, one action's outputs) and discard the rest before reasoning about it.actionName to get_live_flow_run_action_outputs. Omitting it fetches all top-level actions. For actions inside a foreach, passing actionName without iterationIndex can return every repetition of that action.\"OperationId\":), so a plain grep for "OperationId": will not match. Parse first, then filter.name + state + trigger for flow lists and actionName + status + code for run errors — not raw JSON, unless asked.# Good — drill into one operation in a connector swagger
conn = mcp("describe_live_connector", {"environmentName": ENV, "connectorName": "shared_sharepointonline"})
op = conn["properties"]["swagger"]["paths"]["/datasets/{dataset}/tables/{table}/items"]["get"]
print(op["operationId"], "—", op.get("summary"))
# Bad — keeping the whole 500 KB swagger in context
print(json.dumps(conn, indent=2)) # don't do this| Field | Value |
|---|---|
| Auth header | x-api-key: <JWT> — not Authorization: Bearer |
| Token format | Plain JWT — do not strip, alter, or prefix it |
| Timeout | Use ≥ 120 s for get_live_flow_run_action_outputs (large outputs) |
| Environment name | Default-<tenant-guid> (find it via list_live_environments or list_live_flows response) |
tool_search)© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/flowstudio-power-automate-mcp of github/awesome-copilot.
Open the folder on GitHubat commit 727ff2e
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Flowstudio Power Automate MCP next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Flowstudio Power Automate MCP this skillgithub/awesome-copilot | 40k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Power Automate MCPLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Power Automate MCPhashgraph-online/awesome-codex-plugins | 1.2k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Copilot SDKaiskillstore/marketplace | 430 | 5 repos | ~3.8k | Automated safety check: Pass | None | |
| Copilot SDKintellectronica/agent-skills | 295 | — | ~3.2k | Automated safety check: Pass | CC0-1.0 | |
| Copilot SDKmicrosoft/skills | 3.1k | — | ~7.1k | Automated safety check: Pass | MIT |
LeoYeAI/openclaw-master-skills
Connect to and operate Power Automate cloud flows via a FlowStudio MCP server.
hashgraph-online/awesome-codex-plugins
Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via listskills / toolsearch, and oversized-response handling.
aiskillstore/marketplace
Build applications that programmatically interact with GitHub Copilot.
intellectronica/agent-skills
This skill helps with GitHub Copilot SDK work across Node.js/TypeScript, Python, Go, .NET, and Java.
microsoft/skills
Build applications powered by GitHub Copilot using the Copilot SDK.
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Categories
Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via listskills / toolsearch, and oversized-response handling. Flowstudio Power Automate MCP is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.js), tool discovery via listskills / toolsearch, and oversized-response handling.
Flowstudio Power Automate MCP fits situations like: tasks that involve MCP servers.
Run `npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a claude-code`. Or copy the skill folder (skills/flowstudio-power-automate-mcp in github/awesome-copilot) into .claude/skills/flowstudio-power-automate-mcp in your project. Claude Code loads it when a task matches its description.
Run `npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a codex`. Or copy the skill folder (skills/flowstudio-power-automate-mcp in github/awesome-copilot) into .agents/skills/flowstudio-power-automate-mcp in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flowstudio-power-automate-mcp, .gemini/skills/flowstudio-power-automate-mcp, .github/skills/flowstudio-power-automate-mcp and .opencode/skills/flowstudio-power-automate-mcp in your project.
Going by SKILL.md and its folder, Flowstudio Power Automate MCP needs the command-line tools its instructions call (pip). Our summary lists: Python 3; Node.js; A credential in YOUR_JWT_TOKEN.
SKILL.md names 3 domains. In commands or code: mcp.flowstudio.app; the agent is likely to contact it when it follows the instructions. As links in the text: github.com and learn.flowstudio.app. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Flowstudio Power Automate MCP is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Flowstudio Power Automate MCP: Power Automate MCP (LeoYeAI/openclaw-master-skills, 2.2k stars), Power Automate MCP (hashgraph-online/awesome-codex-plugins, 1.2k stars), Copilot SDK (aiskillstore/marketplace, 430 stars) and Copilot SDK (intellectronica/agent-skills, 295 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.