TOPY.AI · AI COO

ai.topyPublished by topy.aiOfficial publisherv0.1.0Updated Oct 29, 2026

Founders' AI COO: every AI cofounder's Routines on time — heartbeat, failures, approvals, reports.

The publisher's own server: TOPY.AI · AI CEO

Overview

AI-generated overview

TOPY.AI AI COO server that lets an assistant monitor scheduled AI cofounder Routines, failures, approvals and weekly operations reports.

What you can do
  • Check scheduler health, daily operations status and the COO's four standing goals
  • Inspect, schedule and run Routines, and review every cofounder's schedule for clashes and gaps
  • Review failed runs, retry only safe ones, and diagnose a stopped scheduler or server resource limits
  • List approvals waiting on the founder and send fresh one-click reminder links
  • Produce weekly operations reports, efficiency metrics, automation sweeps and vendor evaluations
When to use it
For founders or small teams running automated AI cofounder Routines on TOPY.AI who want an assistant to watch for failures, keep approvals moving, and summarize operations weekly. Useful when you already have a TOPY.AI account with a OneMan operation.
Requirements
A TOPY.AI account with OAuth, or a TOPY API key in TOPY_API_KEY (or a one-time login via the npm package). Remote endpoint at topy.ai/mcp/coo, or the local stdio package @topy-ai/coo-mcp, which forwards to that endpoint. Only accounts that own the OneMan operation see its Routines and runs.
Before you install
OAuth grants access to your TOPY.AI account; the API key in TOPY_API_KEY is a secret. Skills can run Routines, retry failed runs and send approval reminder emails, which changes state and contacts the founder. Approvals themselves stay with the founder's own one-click links, and the skills state they never handle keys or passwords.

Installation

In SourceWeft

  1. Open TOPY.AI · AI COO in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.topy%2Fcoo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "topy-ai-ai-coo": {
      "type": "http",
      "url": "https://topy.ai/mcp/coo"
    }
  }
}

README

[TOPY AI COO]

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.

[npm] [MIT License] [MCP]


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.

  • Core (topy-ai-coo): connect, the daily operations check, the COO's goals.
  • Routines: schedule a new Routine (daily or weekly, off the hour, clear of the others), check every schedule, run a Routine now.
  • Incidents: failed runs and safe retries only (a failure on a read with nothing sent or written outside, once a day; permission and token errors go to a person), and what to do when the scheduler itself stops.
  • Approvals: what waits on the founder, and fresh one-click links for the ones that waited too long.
  • Reporting: the weekly operations report to the founder and the CEO, efficiency, an automation sweep, tool and vendor evaluation.

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.

Install

sh
npx @topy-ai/coo-skills install                  # this project, for the agents set up herenpx @topy-ai/coo-skills install -g --mcp         # your user, plus the MCP servernpx @topy-ai/coo-skills install --category incidents,approvalsnpx @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.

Connect TOPY.AI

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.

ClientHow
Claude, ChatGPT (web, desktop)custom connector https://topy.ai/mcp/coo
Claude Codeclaude mcp add --transport http topy-coo https://topy.ai/mcp/coo
Codexcodex mcp add topy-coo --url https://topy.ai/mcp/coo
Clients that only start a commandnpx -y @topy-ai/coo-mcp after npx @topy-ai/coo-mcp login
Terminal and scriptsnpm i -g @topy-ai/coo-cli && coo-cli login; coo-cli health, coo-cli waiting, coo-cli runs

How the skills fit together

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"

Packages

PackageWhat it is
@topy-ai/coo-skillsThis installer (Claude Code, Codex, Pi, Cursor, Gemini CLI, …)
@topy-ai/coo-mcpThe COO MCP server as a local stdio server (forwards to https://topy.ai/mcp/coo)
@topy-ai/coo-cliThe AI COO on the command line

Repository structure

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 marketplaceskills.json                         machine-readable cataloguepackages/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.

License

MIT © TOPY AI LTD. Privacy: topy.ai/privacy.

Skills

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.

AI COO core (MCP) · topy-ai-coo

SkillTierWhat it does
topy-coo-connectcoreConnects 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-checkcoreThe 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-goalscoreThe 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.

Routines & schedules · topy-ai-coo-routines

SkillTierWhat it does
topy-coo-run-routineconnectedRuns 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-checkconnectedChecks 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-routineconnectedPicks 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.

Incidents & retries · topy-ai-coo-incidents

SkillTierWhat it does
topy-coo-failed-runsconnectedLooks 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-downconnectedWhen 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-healthconnectedReads 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.

Approvals · topy-ai-coo-approvals

SkillTierWhat it does
topy-coo-approval-remindersconnectedSends 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-approvalsconnectedShows 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.

Reporting & improvement · topy-ai-coo-reporting

SkillTierWhat it does
topy-coo-automation-sweepconnectedFinds 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-efficiencyconnectedMeasures 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-evaluationconnectedCompares 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-reportconnectedThe 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.

Source: README.md at commit a7ef4d5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Topy integrations