Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Founders' AI COO: every AI cofounder's Routines on time — heartbeat, failures, approvals, reports.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TOPY_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://topy.ai/mcp/coo打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"coo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http coo https://topy.ai/mcp/cooclaude mcp add coo --env TOPY_API_KEY=your-value -- npx -y @topy-ai/coo-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"coo": {
"url": "https://topy.ai/mcp/coo"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"coo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"coo": {
"type": "http",
"url": "https://topy.ai/mcp/coo"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"coo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://topy.ai/mcp/coo菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 topy.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TOPY_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.1.0)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AvaHR
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
TOPY AI COO Skills 14 skills that make your coding agent a small company's AI COO: every AI cofounder's Routines on time, failures never silent, approvals that don't pile up, and a weekly operations report to the founder and the CEO — on the TOPY.AI COO MCP server.
The AI COO is goal-first. It keeps four standing goals — on time (the scheduler ticks every 5 minutes), no silent failure (every failed run known within 24 hours), approvals flowing (nothing waits on the founder over a day) and less founder time per outcome — and every skill below exists to move one of them.
topy-ai-coo): connect, the daily operations check, the COO's goals.The operating rules come from running the AI CEO's and AI CFO's Routines in production, and from Maggie Ops' autopilot: every run is recorded, a job runs once per period, retries never repeat something that may already have taken effect, and every Routine ends in a report. Skills never approve a step for the founder (approvals are the founder's own one-click links), never confirm a change for you, and never handle keys or passwords.
npx @topy-ai/coo-skills install # this project, for the agents set up here
npx @topy-ai/coo-skills install -g --mcp # your user, plus the MCP server npx @topy-ai/coo-skills install --category incidents,approvals npx @topy-ai/coo-skills list
Claude Code plugins: /plugin marketplace add TOPY-AI-LTD/TOPY-AI-COO-Skills, then /plugin install topy-ai-coo-all@topy-ai-coo. Codex: codex plugin marketplace add TOPY-AI-LTD/TOPY-AI-COO-Skills. Pi: pi install npm:@topy-ai/coo-skills. See the installer README.
https://topy.ai/mcp/coo — OAuth with your TOPY.AI account (the same one as the AI CEO and AI CFO). Only the accounts that own the OneMan operation see its Routines and runs.
| Client | How |
|---|---|
| Claude, ChatGPT (web, desktop) | custom connector https://topy.ai/mcp/coo |
| Claude Code | claude mcp add --transport http topy-coo https://topy.ai/mcp/coo |
| Codex | codex mcp add topy-coo --url https://topy.ai/mcp/coo |
| Clients that only start a command | npx -y @topy-ai/coo-mcp after npx @topy-ai/coo-mcp login |
| Terminal and scripts | npm i -g @topy-ai/coo-cli && coo-cli login; coo-cli health, coo-cli waiting, coo-cli runs |
topy-coo-connect ─▶ topy-coo-goals
│ daily: topy-coo-daily-check ─▶ topy-coo-failed-runs (safe retries) · topy-coo-waiting-approvals topy-coo-approval-reminders (17:13) · watchdog alert ─▶ topy-coo-scheduler-down │ weekly: topy-coo-weekly-report ─▶ topy-coo-efficiency · topy-coo-schedule-check │ change: topy-coo-automation-sweep ─▶ topy-coo-schedule-routine ─▶ topy-coo-run-routine topy-coo-vendor-evaluation
Try: *"Did anything fail last night?"*, *"What's waiting on me?"*, *"Schedule this every Monday morning"*, *"Send the weekly operations report"*, *"The routines stopped"*
| Package | What it is |
|---|---|
@topy-ai/coo-skills | This installer (Claude Code, Codex, Pi, Cursor, Gemini CLI, …) |
@topy-ai/coo-mcp | The COO MCP server as a local stdio server (forwards to https://topy.ai/mcp/coo) |
@topy-ai/coo-cli | The AI COO on the command line |
plugins/
topy-ai-coo/ core skills + .mcp.json (Claude Code) and mcp.json (Codex) topy-ai-coo-routines/ topy-ai-coo-incidents/ topy-ai-coo-approvals/ topy-ai-coo-reporting/ topy-ai-coo-all/ bundle that depends on all five .claude-plugin/marketplace.json Claude Code marketplace .agents/plugins/marketplace.json Codex marketplace skills.json machine-readable catalogue packages/skills/ the @topy-ai/coo-skills installer
The skills are generated from a source catalogue kept next to TOPY.AI's MCP server; the build checks every tool a skill names against the COO server's tool list. Please open an issue rather than editing a SKILL.md.
MIT © TOPY AI LTD. Privacy: topy.ai/privacy.
15 skills in 5 plugins, plus the topy-ai-coo-all bundle. Generated from the source catalogue: please open an issue rather than editing a SKILL.md.
topy-ai-coo| Skill | Tier | What it does |
|---|---|---|
topy-coo-connect | core | Connects the founder's AI COO — the TOPY COO MCP server on the same TOPY account as the AI CEO and CFO — and checks that OneMan's Routine scheduler, approval links and Founder email are set up. |
topy-coo-daily-check | core | The founder's morning operations check: is the scheduler alive, what failed overnight (safe ones retried once), what waits on the founder — quiet when all is well. |
topy-coo-goals | core | The AI COO's four standing goals — Routines run on time, no silent failure, approvals flowing, less founder time per outcome — measured from the scheduler's records, with the status the COO reports to the CEO. |
topy-ai-coo-routines| Skill | Tier | What it does |
|---|---|---|
topy-coo-run-routine | connected | Runs one Routine now through the scheduler (the same policy gate and approvals as a scheduled run) and reads back where it stopped — for a first try, or to catch up after a fix. |
topy-coo-schedule-check | connected | Checks every cofounder's scheduled Routines against the scheduling rules — runs a day, on-the-hour starts, clashes, the daily cap, missing inputs and Routines that never report — and proposes fixes. |
topy-coo-schedule-routine | connected | Picks a good schedule for a new Routine — daily or weekly, off the hour, clear of the other Routines, within the daily cap — and checks it before it goes on the scheduler. |
topy-ai-coo-incidents| Skill | Tier | What it does |
|---|---|---|
topy-coo-failed-runs | connected | Looks at failed Routine runs, reruns once the ones that are safe (failed on a read, nothing sent or written outside, not a permission or token error) and hands the rest to a person with the reason. |
topy-coo-scheduler-down | connected | When the Routine scheduler stops ticking (the routine-watchdog email, or the COO's health check says down): confirm it, say what is not running, and walk whoever has server access through the checks — without guessing a fix. |
topy-coo-server-health | connected | Reads disk (every mount and its inodes), memory, swap and load on the founder's servers and the OneMan host, says what is near its limit and how soon a growing disk fills, and names who should act — without deleting or restarting anything. |
topy-ai-coo-approvals| Skill | Tier | What it does |
|---|---|---|
topy-coo-approval-reminders | connected | Sends the founder a fresh one-click approval email for runs waiting longer than a threshold (default 24 hours) — once a day per run, never more. |
topy-coo-waiting-approvals | connected | Shows every Routine paused on the founder — what it waits for, what it found so far, since when, when the link expires — so the founder can decide in one sitting. |
topy-ai-coo-reporting| Skill | Tier | What it does |
|---|---|---|
topy-coo-automation-sweep | connected | Finds repeated manual work (done three times or more) worth turning into a Routine or a service, drafts the Routine's steps and schedule, and leaves the go-ahead to the founder. |
topy-coo-efficiency | connected | Measures how well the Routines run — success rate, retries, cost and failures by cofounder and step — and finds the few changes that would raise reliability or cut founder time. |
topy-coo-vendor-evaluation | connected | Compares tools, vendors or contractors on weighted criteria and value for money, and recommends one with the reasons — a method that works with or without TOPY. |
topy-coo-weekly-report | connected | The week's operations for the founder (branded email) and the CEO: runs by cofounder, success rate, what fails most, schedule problems and what waits on the founder. |