Deploy CenterSmall add-ons that call the deploys CLI. Each one only reads, except the GitHub Action when a
workflow sets deploy: true (also the digest's approve workflow, after a person approved), the MCP server when it is started with DEPLOYS_MCP_ALLOW_DEPLOY=1, and the Raycast extension after you confirm a deploy. Auto-deploy
stays off: nothing here deploys unless a person asks for it.
| Folder | What it does |
|---|---|
| GitHub Action | A GitHub Action that lists what has changes (deploys changed --json), and deploys only with deploy: true. It includes an example workflow for a [deploy] commit marker. |
| pre-push hook | A git pre-push hook. It warns how many builds a push would start on projects that still deploy on push. |
| Status badges | An SVG badge per project, for example deployed · 3 d ago · 4 commits waiting. No server needed. |
| Status page | A static "what shipped when" page (index.html, an Atom feed, status.json) for the projects you list, with an optional site check. Any static host. |
| Daily summary | A daily summary ("live today / waiting") sent to one webhook: Discord, Slack-compatible, ntfy or Telegram. |
| Claude Code plugin | A Claude Code plugin: a skill, /deploys-* commands, and a read-only reminder after git push. It deploys only after you say yes. Install: /plugin marketplace add Pschmetzer/deploy-center, then /plugin install deploy-center@deploy-center. See Claude Code. |
| MCP server | An MCP server for AI coding agents (Claude Code, Claude Desktop, Cursor, VS Code). Read-only tools for what is waiting, building, release notes and logs; deploy and rollback of one project only with DEPLOYS_MCP_ALLOW_DEPLOY=1. |
| Raycast extension | A Raycast extension: Waiting Deploys, Deploy Status and Deploy All Changed. It deploys only after a confirmation. Not on the Raycast Store yet (PUBLISHING.md). |
| VS Code extension | A VS Code extension, also for Cursor and Windsurf (Open VSX): ⏳ 3 waiting in the status bar for this folder's repo, a project tree, deploy with confirmation, the build log and "Copy for AI". Deploys only after a click and a confirmation. |
| Agent digest | A daily digest of what waits, agent and human commits apart, as Markdown, an issue and a webhook message. A person approves with a button or the deploy-approved label; an example workflow then deploys only the approved projects. |
| Docker image | A Linux image with deploys and its tools, for CI. |
| Verify a release | How to check a release: SHA-256, codesign, spctl. |
Tests: integrations/tests/run.sh. They use a stand-in deploys, curl and gh, so they need no
network and no accounts. The MCP tests also need node and npm ci in mcp/, and are skipped
without them.
Reading every project#
The badge, notify, the status page and the hook need every project, including the ones that are up to
date. That is deploys list --json: every provider that is on and set up (see lib/projects.sh).
Render is read only when a key is there, in RENDER_API_KEY or the Mac keychain. With a Render
key that is wrong or expired, deploys render list --json currently does not come back. Set a
working key, or remove the wrong one.