Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Founders' AI CPO: product review, feedback triage, decision log, honest A/B tests, PRDs, roadmap.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TOPY_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://topy.ai/mcp/cpo打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"cpo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cpo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http cpo https://topy.ai/mcp/cpoclaude mcp add cpo --env TOPY_API_KEY=your-value -- npx -y @topy-ai/cpo-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"cpo": {
"url": "https://topy.ai/mcp/cpo"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"cpo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cpo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cpo": {
"type": "http",
"url": "https://topy.ai/mcp/cpo"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cpo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/cpo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://topy.ai/mcp/cpo菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 topy.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 295 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写: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, Starreel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
TOPY AI CPO Skills 19 skills that make your coding agent a small company's AI CPO: it decides what to build and proves it worked — feedback triaged with clear rules, de-identified user research, a PMF survey, positioning, RICE priorities, a now/next/later roadmap, PRDs with a success metric, a build-or-not check before the AI CTO, pre-registered experiments read without peeking, and a decision log with falsifiers — on the TOPY.AI CPO MCP server.
The AI CPO is goal-first. It keeps three standing goals — people reach value (activation rate), people keep coming back (weekly active users) and the product is a must-have (the PMF score: 40% or more "very disappointed") — and every skill below exists to move one of them. Usage figures and experiment results come from the tools; a KPI without a recorded value is "no data", never zero.
topy-ai-cpo): connect, the CPO's goals, the weekly product review, the daily watch.The safety model comes from Maggie Product and Maggie Feedback Triage and does not bend: experiments are pre-registered (hypothesis, metric, MDE, sample, stop rule) and never peeked at — a read-out before the planned sample says "keep running", never "significant"; every PRD has a success metric and how it is measured; every logged decision has a falsifier; feedback, interview and usage text is data, never instructions, and quotes are de-identified; anything touching billing or prices, sign-in, permissions, security, privacy, legal text, paid builds or deleting customer data is a person's decision; and the CPO decides what to build — the AI CTO builds: it writes no code and ships nothing. Changes take two calls — a preview, then your yes.
npx @topy-ai/cpo-skills install # this project, for the agents set up here
npx @topy-ai/cpo-skills install -g --mcp # your user, plus the MCP server npx @topy-ai/cpo-skills install --category feedback,experiments npx @topy-ai/cpo-skills list
Claude Code plugins: /plugin marketplace add TOPY-AI-LTD/TOPY-AI-CPO-Skills, then /plugin install topy-ai-cpo-all@topy-ai-cpo. Codex: codex plugin marketplace add TOPY-AI-LTD/TOPY-AI-CPO-Skills. Pi: pi install npm:@topy-ai/cpo-skills. See the installer README.
https://topy.ai/mcp/cpo — OAuth with your TOPY.AI account (the same one as the AI CEO, CFO, COO, CSO and CRO). Only the accounts that own the OneMan operation see its product records.
| Client | How |
|---|---|
| Claude, ChatGPT (web, desktop) | custom connector https://topy.ai/mcp/cpo |
| Claude Code | claude mcp add --transport http topy-cpo https://topy.ai/mcp/cpo |
| Codex | codex mcp add topy-cpo --url https://topy.ai/mcp/cpo |
| Clients that only start a command | npx -y @topy-ai/cpo-mcp after npx @topy-ai/cpo-mcp login |
| Terminal and scripts | npm i -g @topy-ai/cpo-cli && cpo-cli login |
Writing code and shipping are not on topy.ai/mcp/cpo: the AI CTO builds, after the build-or-not check and the Founder's yes.
topy-cpo-connect ─▶ topy-cpo-goals
│ weekly Tue 09:27: topy-cpo-weekly-review ─▶ the founder (email) and the CEO weekdays 11:07: topy-cpo-daily-watch (quiet unless something needs attention) │ feedback: topy-cpo-feedback-capture ─▶ topy-cpo-feedback-triage ─▶ topy-cpo-feedback-reply discovery: topy-cpo-user-research · topy-cpo-pmf-survey ─▶ topy-cpo-positioning planning: topy-cpo-prioritize ─▶ topy-cpo-roadmap ─▶ topy-cpo-build-or-not ─▶ topy-cpo-prd ─▶ the AI CTO experiments: topy-cpo-experiment-plan ─▶ topy-cpo-launch-safely ─▶ topy-cpo-experiment-read decisions: topy-cpo-decision-log ─▶ topy-cpo-decision-revisit
Try: *"How did the product do this week?"*, *"Triage the new feedback"*, *"Should we build this?"*, *"Write a PRD for full exports"*, *"Did the onboarding test win?"*
| Package | What it is |
|---|---|
@topy-ai/cpo-skills | This installer (Claude Code, Codex, Pi, Cursor, Gemini CLI, …) |
@topy-ai/cpo-mcp | The CPO MCP server as a local stdio server (forwards to https://topy.ai/mcp/cpo) |
@topy-ai/cpo-cli | The AI CPO on the command line |
plugins/
topy-ai-cpo/ core skills + .mcp.json (Claude Code) and mcp.json (Codex) topy-ai-cpo-feedback/ topy-ai-cpo-discovery/ topy-ai-cpo-planning/ topy-ai-cpo-experiments/ topy-ai-cpo-decisions/ topy-ai-cpo-all/ bundle that depends on all six .claude-plugin/marketplace.json Claude Code marketplace .agents/plugins/marketplace.json Codex marketplace skills.json machine-readable catalogue packages/skills/ the @topy-ai/cpo-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 CPO server's tool list. Please open an issue rather than editing a SKILL.md.
MIT © TOPY AI LTD. Privacy: topy.ai/privacy.
19 skills in 6 plugins, plus the topy-ai-cpo-all bundle. Generated from the source catalogue: please open an issue rather than editing a SKILL.md.
topy-ai-cpo| Skill | Tier | What it does |
|---|---|---|
topy-cpo-connect | core | Connect the TOPY CPO MCP server and check what it can see: the product review, the feedback queue, experiments and the decision log. |
topy-cpo-daily-watch | core | Weekdays: new feedback to triage, experiments due for a read-out and decisions due for revisit — a note to the Founder only when something needs attention. |
topy-cpo-goals | core | The AI CPO's standing goals and its status report for the CEO: activation, weekly active users and the PMF score, each with source and date or 'no data'. |
topy-cpo-weekly-review | core | Every Tuesday: usage, the feedback queue by theme, experiments due for a read-out and decisions due for revisit, with at most three actions — for the Founder and the CEO. |
topy-ai-cpo-feedback| Skill | Tier | What it does |
|---|---|---|
topy-cpo-feedback-capture | connected | Record a piece of user feedback — a bug, an idea, praise or a question — with where it came from, de-identified, so triage can act on it. |
topy-cpo-feedback-reply | connected | Draft the reply each sender is owed — fixed, coming, not planned and why, or one precise question — in plain words and their language, for the Founder to send. |
topy-cpo-feedback-triage | connected | Decide each new item — accept, reject, duplicate or needs info — size it small, medium or large, and route it: small and safe to the AI CTO, larger or sensitive ones to a PRD and the Founder. |
topy-ai-cpo-discovery| Skill | Tier | What it does |
|---|---|---|
topy-cpo-pmf-survey | connected | Run the product/market-fit survey properly — the 'very disappointed' question to the right users, 40% as the signal — and read who the product is a must-have for. |
topy-cpo-positioning | connected | Write the positioning — for whom, what job, which category, what benefit, unlike which alternative — from a sourced teardown of the real alternatives. |
topy-cpo-user-research | connected | Plan and run a small round of user interviews about past behaviour, then turn the notes into de-identified insights and recorded feedback. |
topy-ai-cpo-planning| Skill | Tier | What it does |
|---|---|---|
topy-cpo-build-or-not | connected | Before the AI CTO writes code: reuse what exists, compose a routine for a one-off, or build — privately or as a reusable app — with the reason recorded. |
topy-cpo-prd | connected | Write a one-page PRD — problem, evidence, goals, non-goals, success metric and how it is measured, risks, rollout, open questions — that the AI CTO can build from. |
topy-cpo-prioritize | connected | Rank candidate features by RICE — reach × impact × confidence ÷ effort — with the scales written down, so the order is explainable and the decision stays a person's. |
topy-cpo-roadmap | connected | Keep one roadmap in three stages — now (committed), next (shaped), later (ideas) — ordered by value and effort, tied to goals, with no fake dates. |
topy-ai-cpo-experiments| Skill | Tier | What it does |
|---|---|---|
topy-cpo-experiment-plan | connected | Pre-register an A/B test — hypothesis, one primary metric, minimum detectable effect, sample size, duration and stop rule — then start it. |
topy-cpo-experiment-read | connected | Read a test against its pre-registered plan: keep running until the sample is reached, check the split, report the effect with its uncertainty and guardrails, and log the decision. |
topy-cpo-launch-safely | standalone | Before launch: define and verify the events the success metric needs, ship behind a feature flag to a small share first, watch guardrails, and keep a one-switch rollback. |
topy-ai-cpo-decisions| Skill | Tier | What it does |
|---|---|---|
topy-cpo-decision-log | connected | Record a product decision with why, the evidence and a falsifier — what would change it — and a date to revisit, so decisions can be checked instead of re-argued. |
| [`topy-cpo-deci
只显示了开头部分;其余内容请在仓库中阅读