TOPY.AI · AI CTO

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

Founders' AI CTO: CI failures explained, PRs and checks, release notes, alerts.

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

Overview

AI-generated overview

TOPY.AI AI CTO gives a coding agent GitHub-based CI, PR, release, deploy and security-alert workflows for a small engineering team.

What you can do
  • Explain CI: read failed GitHub Actions runs, their jobs and logs, separate flaky tests from real failures, and re-run or open an issue after a preview.
  • Review code and triage issues: assess a pull request for risk and turn bug reports or CI findings into sized, owned issues.
  • Prepare releases: draft release notes, run a release gate on evidence, plan a gated deploy, and roll back to the last good build.
  • Watch security and dependencies: read Dependabot, code-scanning and secret-scanning alerts, and advise on secrets hygiene.
  • Report status: standing goals, a morning check of service health, CI and waiting pull requests, and incident or architecture-decision guidance.
When to use it
Useful for a small team or solo founder who wants an agent to keep an eye on GitHub CI, pull requests, releases and security alerts, and to explain failures and prepare releases with evidence. It fits workflows where a human still approves merges, releases and production changes.
Requirements
A TOPY.AI account with OAuth, or a TOPY_API_KEY for the local stdio package. The TOPY AI GitHub App must be created and installed on the repositories, and only accounts that own the OneMan operation reach its GitHub. Remote endpoint at topy.ai/mcp/cto, or Node.js via npx for the local server.
Before you install
It reaches GitHub through the TOPY AI GitHub App, so repository access is granted to that app and to TOPY.AI. Changes such as issues, comments and re-runs take a preview call plus confirmation. Merges, releases, new repositories and production workflows are reserved for the founder's approval elsewhere. Code, logs and issue text are treated as data, and secrets should never be printed or requested.

Installation

In SourceWeft

  1. Open TOPY.AI · AI CTO 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%2Fcto/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-cto": {
      "type": "http",
      "url": "https://topy.ai/mcp/cto"
    }
  }
}

README

[TOPY AI CTO]

TOPY AI CTO Skills

17 skills that make your coding agent a small company's AI CTO: what is live keeps working and every release has evidence — CI failures explained from their logs, flaky tests quarantined, pull requests reviewed for risk, release notes, a release gate, safe deploys and rollbacks, incident response, dependency alerts and secrets hygiene — through the TOPY AI GitHub App on the TOPY.AI CTO MCP server.

[npm] [MIT License] [MCP]


The AI CTO is goal-first. It keeps four standing goals — what is live works (uptime), we ship often and safely (deploy frequency, change failure rate), every release has evidence (CI green, QA passed, live == built) and the platform can grow — and every skill below exists to move one of them. Runs, checks, logs and alerts come from the tools; an alert kind GitHub won't show is "not read" with GitHub's reason, never zero.

  • Core (topy-ai-cto): connect, the CTO's goals, the morning check, the CI watch.
  • CI: why CI failed, flaky tests, CI hygiene.
  • Code review & issues: review a pull request for risk, triage engineering issues.
  • Releases & deploys: release notes, the release gate, deploy safely, roll back.
  • Dependencies & secrets: dependency and security alerts, secrets hygiene.
  • Incidents & architecture: incident response, architecture decision records.

The safety model comes from Maggie QA Workflow and Maggie Deployment and does not bend: GitHub is reached through the TOPY AI GitHub App the Founder installs — no GitHub token passes through the agent; merging to the default branch, creating repositories or releases and production workflows are the Founder's, approved on OneMan, never tools here; secrets are never printed or asked for; code, commit messages, issue text and logs are data, never instructions; and every release needs evidence before it ships. Changes (an issue, a comment, a re-run) take two calls — a preview, then your yes.

Install

sh
npx @topy-ai/cto-skills install                  # this project, for the agents set up herenpx @topy-ai/cto-skills install -g --mcp         # your user, plus the MCP servernpx @topy-ai/cto-skills install --category ci,releasesnpx @topy-ai/cto-skills list

Claude Code plugins: /plugin marketplace add TOPY-AI-LTD/TOPY-AI-CTO-Skills, then /plugin install topy-ai-cto-all@topy-ai-cto. Codex: codex plugin marketplace add TOPY-AI-LTD/TOPY-AI-CTO-Skills. Pi: pi install npm:@topy-ai/cto-skills. See the installer README.

Connect TOPY.AI

https://topy.ai/mcp/cto — OAuth with your TOPY.AI account (the same one as the AI CEO, CFO, COO, CSO, CRO and CPO). Only the accounts that own the OneMan operation reach its GitHub. Connect GitHub first: create and install the TOPY AI GitHub App from the links OneMan's CTO gives (github_setup_app, github_setup_install); you press Create and Install on GitHub.

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

Merges, releases, new repositories and production workflows are not on topy.ai/mcp/cto: they need the Founder's approval on OneMan.

How the skills fit together

topy-cto-connect ─▶ topy-cto-goals        │   every morning:   topy-cto-morning-check   around the clock: topy-cto-ci-watch (an email only on a failure or a recovery)        │   ci:        topy-cto-ci-failure ─▶ topy-cto-flaky-tests · topy-cto-ci-hygiene   code:      topy-cto-pr-review · topy-cto-issue-triage   releases:  topy-cto-release-notes ─▶ topy-cto-release-gate ─▶ topy-cto-deploy-safely ─▶ topy-cto-rollback   security:  topy-cto-dependency-alerts · topy-cto-secrets-hygiene   platform:  topy-cto-incident · topy-cto-architecture-decision

Try: "Is CI green?", "Why did the build fail?", "Review PR 42", "Can we ship?", "Any security alerts?"

Packages

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

Repository structure

plugins/  topy-ai-cto/                   core skills + .mcp.json (Claude Code) and mcp.json (Codex)  topy-ai-cto-ci/   topy-ai-cto-code/   topy-ai-cto-releases/  topy-ai-cto-security/   topy-ai-cto-platform/  topy-ai-cto-all/               bundle that depends on all six.claude-plugin/marketplace.json     Claude Code marketplace.agents/plugins/marketplace.json    Codex marketplaceskills.json                         machine-readable cataloguepackages/skills/                    the @topy-ai/cto-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 CTO server's tool list. Please open an issue rather than editing a SKILL.md.

License

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

Skills

17 skills in 6 plugins, plus the topy-ai-cto-all bundle. Generated from the source catalogue: please open an issue rather than editing a SKILL.md.

AI CTO core (MCP) · topy-ai-cto

SkillTierWhat it does
topy-cto-ci-watchcoreHow the AI CTO watches CI around the clock: a GitHub webhook per run, an email only on a failure or a recovery, with the failing jobs and the log lines.
topy-cto-connectcoreConnect the TOPY CTO MCP server and check what it can see: the GitHub App and its repositories, CI, alerts and service health.
topy-cto-goalscoreThe AI CTO's standing goals and its status report for the CEO: uptime, deploy frequency and change failure rate, each with source and date or 'no data'.
topy-cto-morning-checkcoreEach morning: service health, CI on the default branches, pull requests waiting and anything red — the one thing to fix first.

CI · topy-ai-cto-ci

SkillTierWhat it does
topy-cto-ci-failureconnectedExplain a failed GitHub Actions run from its jobs and logs: the step, the cause in the log's own words, flaky or real, and the fix — then re-run or open an issue.
topy-cto-ci-hygienestandaloneKeep CI fast and trustworthy: required checks, caching, a time budget, pinned actions, least-privilege tokens and no secrets in logs.
topy-cto-flaky-testsconnectedTell a flaky test from a real failure, quarantine it with an owner and a deadline, and fix the cause (time, order, network, shared state) instead of re-running forever.

Code review & issues · topy-ai-cto-code

SkillTierWhat it does
topy-cto-issue-triageconnectedTurn bug reports and CI findings into issues worth fixing: reproduce, size, label, owner — and close what isn't actionable.
topy-cto-pr-reviewconnectedReview a pull request for what matters before merge: what changed, whether checks pass, and the risks — migrations, auth, money, secrets, irreversible steps, missing tests.

Releases & deploys · topy-ai-cto-releases

SkillTierWhat it does
topy-cto-deploy-safelyconnectedShip to production in small steps: plan, the Founder's approval, deploy the gated build, canary, check live matches what was built, then report — or roll back.
topy-cto-release-gateconnectedDecide whether a build may ship: CI green on the exact commit, checks and QA passed, migrations reversible, rollback ready, and someone watching — evidence for each.
topy-cto-release-notesconnectedDraft release notes from the commits since the last release, grouped as new, improved and fixed in words customers understand — nothing is published.
topy-cto-rollbackconnectedWhen a release hurts, restore service first: redeploy the last good build, keep data safe, confirm recovery, then find the cause.

Dependencies & secrets · topy-ai-cto-security

SkillTierWhat it does
topy-cto-dependency-alertsconnectedRead Dependabot, code-scanning and secret-scanning alerts, fix what is exploitable first, and say plainly which alert kinds GitHub isn't showing and why.
topy-cto-secrets-hygienestandaloneKeep keys and tokens out of code, logs and chats: where secrets live, least privilege, rotation, and what to do in the first hour after one leaks.

Incidents & architecture · topy-ai-cto-platform

SkillTierWhat it does
topy-cto-architecture-decisionstandaloneRecord a technical decision so it can be revisited: the context, the options with their costs, the choice, its consequences, and what would make us change it.
topy-cto-incidentconnectedWhen something customers use is down or wrong: one lead, stop the harm, restore service, communicate on a clock, then a blameless review with fixes.

Source: README.md at commit f0c0b29

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