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/ctoClaude 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메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 topy.ai 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: TOPY_API_KEY
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0)은 10일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 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. |