Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Debug, build, and manage Power Automate cloud flows with AI agents
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
x-api-key标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp --header 'x-api-key: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"flowstudio": {
"url": "https://mcp.flowstudio.app/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"flowstudio": {
"type": "http",
"url": "https://mcp.flowstudio.app/mcp",
"headers": {
"x-api-key": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
x-api-key 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 ninihen1 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:x-api-key
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Claude Checkpoint MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server that checkpoints Claude Code session context to survive crashes and token limits
按原文从作者的仓库复制。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.
MIT
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