Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Founders' AI COO: every AI cofounder's Routines on time — heartbeat, failures, approvals, reports.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
TOPY_API_KEYAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://topy.ai/mcp/cooÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"coo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Führe das in deinem Terminal aus
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-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"coo": {
"url": "https://topy.ai/mcp/coo"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"coo": {
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"coo": {
"type": "http",
"url": "https://topy.ai/mcp/coo"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"coo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/coo-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://topy.ai/mcp/cooMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain topy.ai bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: TOPY_API_KEY
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.0) kam vor 10 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, HotCodePush
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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. |