DeployAngel verifies every production deploy of a Rails, Django, FastAPI, or Flask app: it compares real traffic after the deploy with the last healthy release, then clears the release, fails it, or says what it's still waiting to see.
The deployangel plugin lets Claude Code, Cursor, and Codex wait for that
verdict after they deploy, and read the evidence when a release fails. See
plugins/deployangel for what it contains and
needs.
Claude Code
claude plugin marketplace add DeployAngel/agent-plugins
claude plugin install deployangel@deployangelCodex
codex plugin marketplace add DeployAngel/agent-pluginsThen install deployangel from the plugin list. Codex starts MCP servers with
a limited environment, so if the server reports a missing token, forward it in
your Codex config:
[mcp_servers.deployangel]
env_vars = ["DEPLOYANGEL_API_TOKEN", "DEPLOYANGEL_URL"]Cursor
Install DeployAngel from the Cursor Marketplace.
Any project, without a plugin
bundle exec deployangel install agents # Rails
deployangel install agents # PythonSet DEPLOYANGEL_API_TOKEN to a "CLI & coding agents" token, from the app's
Settings in DeployAngel, in the environment your agent runs in. Keep it out
of the repository.
One plugin, described for each tool:
| Tool | Marketplace | Plugin manifest | MCP servers |
|---|---|---|---|
| Claude Code | .claude-plugin/marketplace.json |
.claude-plugin/plugin.json |
.mcp.json |
| Cursor | .cursor-plugin/marketplace.json |
.cursor-plugin/plugin.json |
mcp.json |
| Codex (Agent Plugins) | .agents/plugins/marketplace.json |
plugin.json |
mcp.json |
All three share skills/verify-deploy/SKILL.md. Keep the two MCP files and
the three manifests in step when you change them.
MIT