Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Founders' AI COO: every AI cofounder's Routines on time — heartbeat, failures, approvals, reports.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TOPY_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://topy.ai/mcp/cooOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"coo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Run this in your terminal
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-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"coo": {
"url": "https://topy.ai/mcp/coo"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"coo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"coo": {
"type": "http",
"url": "https://topy.ai/mcp/coo"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"coo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://topy.ai/mcp/cooMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain topy.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TOPY_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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. |