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/cpoClaude 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메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 topy.ai 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: TOPY_API_KEY
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0)은 10일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Reelsaw
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ 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.
Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.
제작자의 저장소에서 쓰인 그대로 가져왔어요. 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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요