Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Founders' AI CTO: CI failures explained, PRs and checks, release notes, alerts.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TOPY_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://topy.ai/mcp/cto打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"cto": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cto-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http cto https://topy.ai/mcp/ctoclaude mcp add cto --env TOPY_API_KEY=your-value -- npx -y @topy-ai/cto-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"cto": {
"url": "https://topy.ai/mcp/cto"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"cto": {
"command": "npx",
"args": [
"-y",
"@topy-ai/cto-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cto": {
"type": "http",
"url": "https://topy.ai/mcp/cto"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"cto": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@topy-ai/cto-mcp"
],
"env": {
"TOPY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://topy.ai/mcp/cto菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 topy.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TOPY_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.1.0)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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.
topy-ai-cto): connect, the CTO's goals, the morning check, the CI watch.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.
npx @topy-ai/cto-skills install # this project, for the agents set up here
npx @topy-ai/cto-skills install -g --mcp # your user, plus the MCP server npx @topy-ai/cto-skills install --category ci,releases npx @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.
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.
| Client | How |
|---|---|
| Claude, ChatGPT (web, desktop) | custom connector https://topy.ai/mcp/cto |
| Claude Code | claude mcp add --transport http topy-cto https://topy.ai/mcp/cto |
| Codex | codex mcp add topy-cto --url https://topy.ai/mcp/cto |
| Clients that only start a command | npx -y @topy-ai/cto-mcp after npx @topy-ai/cto-mcp login |
| Terminal and scripts | npm 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.
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?"*
| Package | What it is |
|---|---|
@topy-ai/cto-skills | This installer (Claude Code, Codex, Pi, Cursor, Gemini CLI, …) |
@topy-ai/cto-mcp | The CTO MCP server as a local stdio server (forwards to https://topy.ai/mcp/cto) |
@topy-ai/cto-cli | The AI CTO on the command line |
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 marketplace skills.json machine-readable catalogue packages/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.
MIT © TOPY AI LTD. Privacy: topy.ai/privacy.
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.
topy-ai-cto| Skill | Tier | What it does |
|---|---|---|
topy-cto-ci-watch | core | How 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-connect | core | Connect the TOPY CTO MCP server and check what it can see: the GitHub App and its repositories, CI, alerts and service health. |
topy-cto-goals | core | The 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-check | core | Each morning: service health, CI on the default branches, pull requests waiting and anything red — the one thing to fix first. |
topy-ai-cto-ci| Skill | Tier | What it does |
|---|---|---|
topy-cto-ci-failure | connected | Explain 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-hygiene | standalone | Keep CI fast and trustworthy: required checks, caching, a time budget, pinned actions, least-privilege tokens and no secrets in logs. |
topy-cto-flaky-tests | connected | Tell 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. |
topy-ai-cto-code| Skill | Tier | What it does |
|---|---|---|
topy-cto-issue-triage | connected | Turn bug reports and CI findings into issues worth fixing: reproduce, size, label, owner — and close what isn't actionable. |
topy-cto-pr-review | connected | Review a pull request for what matters before merge: what changed, whether checks pass, and the risks — migrations, auth, money, secrets, irreversible steps, missing tests. |
topy-ai-cto-releases| Skill | Tier | What it does |
|---|---|---|
topy-cto-deploy-safely | connected | Ship 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-gate | connected | Decide 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-notes | connected | Draft release notes from the commits since the last release, grouped as new, improved and fixed in words customers understand — nothing is published. |
topy-cto-rollback | connected | When a release hurts, restore service first: redeploy the last good build, keep data safe, confirm recovery, then find the cause. |
topy-ai-cto-security| Skill | Tier | What it does |
|---|---|---|
topy-cto-dependency-alerts | connected | Read 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-hygiene | standalone | Keep 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. |
topy-ai-cto-platform| Skill | Tier | What it does |
|---|---|---|
topy-cto-architecture-decision | standalone | Record 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-incident | connected | When something customers use is down or wrong: one lead, stop the harm, restore service, communicate on a clock, then a blameless review with fixes. |