World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Debug, build, and manage Power Automate cloud flows with AI agents
使っているAIアプリを選んで、設定をコピーしてください。
チェック 5/5 合格 · 質問内容は提供元のサーバー(mcp.flowstudio.app)を通ります · ✓ コマンド確認済み 2026年11月13日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 5 分
Power Automate MCP Server by Flow Studio のキーが必要です(提供元のサイトで作成) · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
Power Automate MCP Server by Flow Studiohttps://mcp.flowstudio.app/mcpRequest headers に、この名前と値を追加
x-api-key<ここにキーを貼り付け>キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Claude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsPower Automate MCP Server by Flow Studio
Power Automate MCP Server by Flow Studio を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Power Automate MCP Server by Flow Studio を使っていると言うか、回答に Power Automate MCP Server by Flow Studio のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT はまだ Power Automate MCP Server by Flow Studio につなげません
Power Automate MCP Server by Flow Studio は接続時に自分のキーが必要ですが、OpenAI のヘルプページは OAuth ログインしか説明しておらず、確認できたキー入力方法がありません
A · Power Automate MCP Server by Flow Studio につなげるアプリを使う
B · その他 の中で ChatGPT につなげる別のサーバー
同じカテゴリでよく使われているものから、キーなしでアドレスだけでつなげるものを選びました
Claude Code につなげます · 約 5 分
Power Automate MCP Server by Flow Studio のキーが必要です(提供元のサイトで作成)
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user flowstudio https://mcp.flowstudio.app/mcp --header 'x-api-key: your-value'Enter の前に「your-value」を自分のキーに書き換えてください
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Power Automate MCP Server by Flow Studio が一覧にあり、接続済みと表示されれば OK です
Power Automate MCP Server by Flow Studio を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が Power Automate MCP Server by Flow Studio を使っていると言うか、回答に Power Automate MCP Server by Flow Studio のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 5 分
Power Automate MCP Server by Flow Studio のキーが必要です(提供元のサイトで作成)
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
Power Automate MCP Server by Flow Studio の設定で x-api-key が空です。自分のキーを入れて保存します
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Power Automate MCP Server by Flow Studio を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が Power Automate MCP Server by Flow Studio を使っていると言うか、回答に Power Automate MCP Server by Flow Studio のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 5 分
Power Automate MCP Server by Flow Studio のキーが必要です(提供元のサイトで作成)
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
Power Automate MCP Server by Flow Studio の設定で x-api-key が空です。自分のキーを入れて保存します
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Power Automate MCP Server by Flow Studio を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Power Automate MCP Server by Flow Studio を使っていると言うか、回答に Power Automate MCP Server by Flow Studio のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
https://mcp.flowstudio.app/mcpJSON 設定は下の「開発者向け」にあります
Claude Code
claude mcp add --transport http --scope user flowstudio https://mcp.flowstudio.app/mcp --header 'x-api-key: your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"flowstudio": {
"url": "https://mcp.flowstudio.app/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"flowstudio": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}説明は自動翻訳です。変数名は原文のままです。迷ったら原文を確認してください。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月13日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
tool_searchFind a tool listed here instead of guessing its name, and get its definition. Query forms: (1) "skill: " — a whole bundle; call list_skills for the names; (2) "select:name1,name2" — exact tools; (3) free text like "cancel run" — ranked against name and description. Non-billable.
list_skillsSkill bundles: groups of the tools listed here that are used together for one task (diagnose-connection-references, build-flow, debug-flow, monitor-flow, discover, governance). Returns each bundle's name and one-line description. Use it when unsure which tools fit a request; tool
report_bugReport a Flow Studio MCP bug or missing capability, append text evidence, or check your reports. Free and available even after quota is reached. Do not include passwords, access tokens, secrets, or full flow definitions unless necessary.
get_taskGet the status and result of a long-running tool call. When a tool replies with a taskId and status "working", the work is still running on the server: do not call that tool again. Wait pollIntervalMs, then call this with the taskId until status is completed or failed. Free.
list_store_flows[Requires Pro+ plan] List Power Automate flows from the Power Clarity cache. Optionally filter by governance flags (monitor, notification rules). Returns key fields including trigger URL, state, and run failure rate. Data is from the stored snapshot — not live from the Power Auto
get_store_flow[Requires Pro+ plan] Get full details for a single Power Automate flow from the Power Clarity cache. Includes trigger URL, owners, state, run statistics, and governance metadata. Data is from the stored snapshot — not live from the Power Automate API.
get_store_flow_runs[Requires Pro+ plan] Get cached run history for a flow from the Power Clarity store. Defaults to the last 7 days. Returns startTime, endTime, status, duration (seconds), failedActions, and remediation hint per run. Data is from the stored snapshot — not live from the Power Automa
get_store_flow_summary[Requires Pro+ plan] Get aggregated run statistics for a flow from the Power Clarity cache: total runs, success count, failure count, success rate, fail rate, and average/max duration over a time window. Data is from the stored snapshot — not live from the Power Automate API.
update_store_flow[Requires Pro+ plan] Update governance/metadata fields on a flow record in the Power Clarity store (description, business impact, owner team, tags, monitor flag, notification settings, etc.). Only fields provided are updated (merge semantics). Writes to the cache — does not call
list_store_environments[Requires Pro+ plan] List all Power Platform environments from the Power Clarity cache.
list_store_makers[Requires Pro+ plan] List all makers (citizen developers / AAD users) from the Power Clarity cache.
get_store_maker[Requires Pro+ plan] Get details for a single maker from the Power Clarity cache by their key (usually the AAD object ID). Includes flow/app counts and whether the account has been deleted.
list_store_power_apps[Requires Pro+ plan] List all Power Apps canvas apps from the Power Clarity cache.
list_store_connections[Requires Pro+ plan] List all Power Platform connections from the Power Clarity cache.
get_live_flow_runsFetch run history for a flow directly from Power Automate. Returns { runs, runCount, triggerChecks }: each run has name, status, startTime, endTime, trigger name/code, and any top-level error. IMPORTANT — no runs does NOT mean the flow is healthy. A trigger that fires and evaluat
get_live_flow_run_errorFetch error details for a specific flow run from the live Power Automate API. Lists every failed action with its error code and message to help diagnose what went wrong.
get_live_flow_run_action_outputsRead the recorded inputs and outputs of actions in one flow run. Without actionName: the top-level actions (optionally filtered by name). With actionName: every execution of that action across foreach iterations, each with repetitionIndexes, status, error, and resolved inputs/out
trigger_live_flowRun a flow on demand — the same as the maker portal's "Run flow" button. Works with Request triggers (HTTP request, manual Button, PowerApps) and with scheduled RECURRENCE flows, which run immediately; a scheduled flow takes no inputs, so passing `body` to one is refused. Pass tr
cancel_live_flow_runCancel a currently running Power Automate flow run via the live PA API. Use after get_live_flow_runs to obtain the run name. Only runs with status "Running" can be cancelled.
resubmit_live_flow_runResubmit a failed or cancelled Power Automate flow run via the live PA API, re-using the original trigger payload. Discovers the trigger name from the flow definition automatically — no trigger name parameter needed.
set_live_flow_stateStart or stop the flow you name. Reads the current state first and only calls Power Automate if a change is actually needed.
get_live_flowFetch the full native Power Automate flow JSON from the PA API, including the complete flow definition (triggers, actions, parameters, outputs). Returns the raw properties object exactly as the PA API returns it. Use this to inspect the full definition before calling update_live_
get_live_flow_versionsList a flow's versions, newest first. A flow in a solution lists every published version. Any other flow lists only versions that ran.
diff_live_flowCompare two versions of a flow. Returns the actions added, removed and changed.
update_live_flowUpdate or create a flow. Use `dryRun: true` to preview any change without writing. Omit flowName to create: definition and displayName are required. Give flowName to update: displayName and/or definition and/or connectionReferences. SURGICAL EDIT: pass `operations` — an ordered l
list_live_environmentsList all Power Platform environments you belong to, directly from Power Automate. Returns id, displayName, sku, location, and state for each environment. mode=all (default) and mode=member: every environment you are a member of. mode=admin: only those you administer; errors rathe
list_live_flowsList Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows you own plus flows shared with you (personal + team), with full definitions. mode=admin: all flows in the environment (require
list_live_connectionsList Power Platform connections in an environment directly from Power Automate. Returns id, displayName, connectorName, environment, createdBy (full object), authenticatedUser, statuses, overallStatus, createdTime, expirationTime, and connectionParameters for each connection. Pas
describe_live_connectorDescribe a live Power Platform connector/API and its operations. Use mode=summary (default) to get a compact operation catalog. Use operationId to describe one operation, including inputs, outputs, dynamic parameter metadata, nextTool hints to call resolve_live_parameters, and an
add_to_solutionAdd a flow or a canvas app to a solution. Pass flowName or app. A flow not yet in a solution moves into `solution`, or into the default solution when it is omitted. A flow or app already in a solution is added to `solution` as well, and stays in the one it is in.
resolve_live_parametersResolve a connector action's inputs the way the flow designer does: dropdown options, list and table columns, folder and file pickers — every input in one call, or one with parameterName. Reads only: it runs the lookups the designer runs, never an action. Pass values you have in
test_live_connectionTest a connection, or run one operation on it. Without operationId it runs the connector's own connection test. With operationId it runs that operation and returns the raw reply: a GET operation, or a lookup the connector itself declares for a dropdown, list, schema or folder pic
create_live_connectionCreate a connection, or sign an existing one in again (pass connectionName). Shows a sign-in card where the person signs in; you never sign in for them. Without the card, give the person signInLink to open. Connectors that use a key or account details instead of a sign-in are ref
read_live_tableRead rows from a Dataverse table, SharePoint list, SQL table or Excel table. Read-only. Returns rows, columns and nextLink.
grant_flow_studio_accessShows a sign-in card; the person signs in, or signs in again when expired. Flow Studio keeps the sign-in for later calls.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月14日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント ninihen1 で確認済みです
コードの最終更新:2 か月前
MITを使用
888ミリ秒で応答(HTTP 200)
サインイン不要
35件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:x-api-key
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は2 か月前、最新バージョン(1.0.0)がレジストリに届いたのは7 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:World Monitor, Claude Flow, Windmill
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Run Windmill scripts and flows and manage jobs, schedules, resources and variables.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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. FlowStudio 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 | FlowStudio 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, ChatGPT, Codex, OpenClaw, Gemini CLI, Cursor, Goose, Amp, OpenHands
Full walkthroughs on learn.flowstudio.app:
Sign in with your Microsoft account instead of pasting a key. Add https://mcp.flowstudio.app/mcp/oauth as a connector in ChatGPT (Developer mode on) or at claude.ai, then follow the sign-in prompt. Walkthrough: ChatGPT for Power Automate.
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: "
Get your token at mcp.flowstudio.app.
Inside a Codex session, install skills directly:
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-mcp
$skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-debug $skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-build $skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-monitoring $skill-installer install https://github.com/ninihen1/power-automate-mcp-skills/tree/main/skills/power-automate-governance
Then connect the MCP server in ~/.codex/config.toml:
[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"
[mcp_servers.flowstudio.http_headers] x-api-key = " "
Search for flowstudio on skills.sh, or:
npx skills add github/awesome-copilot -s flowstudio-power-automate-mcp
npx skills add github/awesome-copilot -s flowstudio-power-automate-debug npx skills add github/awesome-copilot -s flowstudio-power-automate-build npx skills add github/awesome-copilot -s flowstudio-power-automate-monitoring npx skills add github/awesome-copilot -s flowstudio-power-automate-governance
npx clawhub@latest install power-automate-mcp
npx smithery skill add flowstudio/power-automate-mcp
Copy the skill folder(s) into your project's .github/skills/ directory (or wherever your agent discovers skills).
Claude Code:
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
--header "x-api-key: "
Codex (~/.codex/config.toml):
[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"
[mcp_servers.flowstudio.http_headers] x-api-key = " "
Copilot / VS Code (.vscode/mcp.json):
{
"servers": { "flowstudio": { "type": "http", "url": "https://mcp.flowstudio.app/mcp", "headers": { "x-api-key": " " } } } }
Get your token at mcp.flowstudio.app.
These are from real production investigations, not demos.
contains(string(...)) crashed on a nested property. Agent traced through parent flow, into child, through loop iterations, and found the failing input. Portal showed "ExpressionEvaluationFailed" with no context.split(Name, ', ') crashed when 38% of records had null Names. Agent traced parent to child to loop to action, found the root cause, and deployed a fix via update_live_flow.https://mcp.flowstudio.app/mcpx-api-key header)skills/
power-automate-mcp/ core connection & operation skill power-automate-debug/ debug workflow skill power-automate-build/ build & deploy skill power-automate-monitoring/ flow health & tenant inventory skill power-automate-governance/ compliance & governance skill examples/ real debugging walkthroughs README.md LICENSE MIT
Works with Copilot, Claude, ChatGPT, and any MCP-compatible agent.
Contributions welcome. Each skill folder must contain a SKILL.md with the required frontmatter. See the existing skills for the format.
Keywords: Power Automate debugging, flow run history, expression evaluation failed, child flow failure, nested action errors, loop iteration output, agent automation MCP, Power Platform AI, flow definition deploy, resubmit failed run, flow monitoring, governance, CoE, orphan detection, connector audit, archive score, maker inventory