Official agent skill

Flowstudio Power Automate MCP

by github in github/awesome-copilot

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.

OfficialMITAuto-check passedAgent Workflows

Install Flowstudio Power Automate MCP

skills CLI
$ npx skills add github/awesome-copilot --skill flowstudio-power-automate-mcp -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot flowstudio-power-automate-mcp --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
flowstudio-power-automate-mcp
GitHub stars
40k
Used in
1 other repo
Token cost
~3.4k tokens
SKILL.md length
1,192 words
Files
5 (incl. references)
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Extract, don't echo. Pull the specific… → Always pass actionName to… → Reuse the spill file within a session.… → …
  • Tasks that involve MCP servers
  • SKILL.md covers Which Skill to Use When, Source of Truth, How Agents Discover Tools and Recommended Language: Python…, plus 6 more sections
  • Calls pip; reaches mcp.flowstudio.app

What it does

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.

When your agent uses it

  • Tasks that involve MCP servers

Example prompts

  • “/flowstudio-power-automate-mcp”

Requirements

  • Python 3
  • Node.js
  • A credential in YOUR_JWT_TOKEN

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Extract, don't echo. Pull the specific field(s) you need (one operationId, one action's outputs) and discard the rest before reasoning…
  2. Always pass actionName to get_live_flow_run_action_outputs. Omitting it fetches all top-level actions. For actions inside a foreach…
  3. Reuse the spill file within a session. Refetching the same connector swagger costs 30+ seconds and produces another spill — cache the path.
  4. Don't grep the spill file for JSON keys directly. Strings are JSON-escaped inside the file (\"OperationId\":), so a plain grep for…
  5. Summarize tool output to the user. Echo name + state + trigger for flow lists and actionName + status + code for run errors — not raw…

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mcp.flowstudio.app

    Also links to:

    • github.com
    • learn.flowstudio.app

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~168
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,192 words, ~3,429 tokens.

Download SKILL.mdSave it as .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.
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 | 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-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
  • 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 inventoryflowstudio-power-automate-monitoring (Pro+)
Tag, audit, classify, score, or offboard flowsflowstudio-power-automate-governance (Pro+)
Just connect, set up auth, write the helper, parse responsesthis 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

PrioritySourceCovers
1Real API responseAlways trust what the server actually returns
2tool_search / list_skillsAuthoritative tool schemas, parameter names, types, required flags
3SKILL docs & reference filesWorkflow 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-toolWhen to call
list_skillsCold 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.

python
# 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:

BundleUse when
create-flowCreating a brand-new flow; includes environment/connection discovery, connector description, dynamic options, and update_live_flow
build-flowReading or modifying an existing flow definition
debug-flowInvestigating failed runs and action-level inputs/outputs
monitor-flowStarting/stopping, triggering, cancelling, or resubmitting runs
discoverEnumerating environments, flows, and connections
governancePro+ 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.

LanguageVerdictNotes
PythonRecommendedClean JSON handling, no escaping issues, all skill examples use it
Node.js (≥ 18)RecommendedNative fetch + JSON.stringify/JSON.parse; no extra packages
PowerShellAvoid for flow operationsConvertTo-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 / BashPossible but fragileShell-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.


Show full SKILL.md (463 more words)Show less

Core MCP Helper (Python)

Use this helper throughout all subsequent operations:

python
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/json and body structure.
  • MCP error: {"code": -32602, ...} → wrong or missing tool arguments. Call tool_search with select:<toolname> to confirm the schema.

Core MCP Helper (Node.js)

Equivalent helper for Node.js 18+ (built-in fetch — no packages required):

js
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 fetch with https.request from the stdlib or install node-fetch.


Verify the Connection

A 3-line smoke test that confirms the token, endpoint, and helper all work:

python
skills = mcp("list_skills", {})
print(f"Connected — {len(skills)} skill bundles available:",
      [s["name"] for s in skills])

Expected output:

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


Handling Oversized Responses

Some MCP tool responses are large enough to overflow the agent's context window:

ToolTypical sizeCause
describe_live_connector100-600 KBFull Swagger spec for a connector
get_live_dynamic_properties50-500 KBDynamic connector field schemas such as SharePoint list columns
get_live_flow_run_action_outputs (no actionName)50 KB – several MBTop-level action outputs; with an action in a foreach, every repetition can be returned
get_live_flow (large flows)50-500 KBDeeply nested branches
list_live_flows (large tenants)50-200 KBHundreds of flow records
When the harness spills to a file

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:

text
[{"type":"text","text":"<JSON-escaped payload>"}]

Two parses to reach a usable object:

python
import json
with open(path) as f:
    raw = json.loads(f.read())
payload = json.loads(raw[0]["text"])
powershell
$payload = ((Get-Content $path -Raw | ConvertFrom-Json)[0].text) | ConvertFrom-Json
Rules of thumb
  1. Extract, don't echo. Pull the specific field(s) you need (one operationId, one action's outputs) and discard the rest before reasoning about it.
  2. Always pass 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.
  3. Reuse the spill file within a session. Refetching the same connector swagger costs 30+ seconds and produces another spill — cache the path.
  4. Don't grep the spill file for JSON keys directly. Strings are JSON-escaped inside the file (\"OperationId\":), so a plain grep for "OperationId": will not match. Parse first, then filter.
  5. Summarize tool output to the user. Echo name + state + trigger for flow lists and actionName + status + code for run errors — not raw JSON, unless asked.
python
# 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

Auth & Connection Notes

FieldValue
Auth headerx-api-key: <JWT> — not Authorization: Bearer
Token formatPlain JWT — do not strip, alter, or prefix it
TimeoutUse ≥ 120 s for get_live_flow_run_action_outputs (large outputs)
Environment nameDefault-<tenant-guid> (find it via list_live_environments or list_live_flows response)

Reference Files

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/flowstudio-power-automate-mcp of github/awesome-copilot.

  • SKILL.md
  • references/MCP-BOOTSTRAP.md
  • references/action-types.md
  • references/connection-references.md
  • references/tool-reference.md

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

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.

Compare with similar skills

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.

Flowstudio Power Automate MCP compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flowstudio Power Automate MCP this skillgithub/awesome-copilot40k1 repos~3.4kAutomated safety check: PassMIT
Power Automate MCPLeoYeAI/openclaw-master-skills2.2k—~4.4kAutomated safety check: PassMIT
Power Automate MCPhashgraph-online/awesome-codex-plugins1.2k—~3.4kAutomated safety check: PassApache-2.0
Copilot SDKaiskillstore/marketplace4305 repos~3.8kAutomated safety check: PassNone
Copilot SDKintellectronica/agent-skills295—~3.2kAutomated safety check: PassCC0-1.0
Copilot SDKmicrosoft/skills3.1k—~7.1kAutomated safety check: PassMIT

Similar skills

  • Power Automate MCP

    LeoYeAI/openclaw-master-skills

    Connect to and operate Power Automate cloud flows via a FlowStudio MCP server.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed
  • Power Automate MCP

    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.

    1.2k GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Copilot SDK

    aiskillstore/marketplace

    Build applications that programmatically interact with GitHub Copilot.

    430 GitHub starsUsed in 5 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Copilot SDK

    intellectronica/agent-skills

    This skill helps with GitHub Copilot SDK work across Node.js/TypeScript, Python, Go, .NET, and Java.

    295 GitHub stars~3.2k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed
  • Copilot SDK

    microsoft/skills

    Official

    Build applications powered by GitHub Copilot using the Copilot SDK.

    3.1k GitHub stars~7.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    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.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    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.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Flowstudio Power Automate MCP

What does Flowstudio Power Automate MCP do?

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.

When should I use Flowstudio Power Automate MCP?

Flowstudio Power Automate MCP fits situations like: tasks that involve MCP servers.

How do I install Flowstudio Power Automate MCP in Claude Code?

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.

How do I install Flowstudio Power Automate MCP in Codex?

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.

Can I use Flowstudio Power Automate MCP in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Flowstudio Power Automate MCP need to run?

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.

Does Flowstudio Power Automate MCP access the network?

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.

Is Flowstudio Power Automate MCP safe to install?

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.

What licence does Flowstudio Power Automate MCP use?

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.

How many tokens does Flowstudio Power Automate MCP use?

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.

What are the alternatives to Flowstudio Power Automate MCP?

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.

Who maintains Flowstudio Power Automate MCP?

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.