DenkOps doesn't have a CLI to learn, an API key to generate, or a dashboard you have to visit first. It's an MCP server that Claude Code talks to directly. Install the plugin, approve a login once, and every deploy after that is a sentence.
The same session keeps working after the deploy: say "read the logs", "rollback", or "status" and Claude calls the matching MCP tool. No context switch to a browser tab, unless something needs a human decision.
Start on DenkOps →Add the DenkOps marketplace and install the plugin (/plugin marketplace add DenkOpsAI/denkops-mcp, then /plugin install denkops), say "log in to DenkOps" and click Approve in the browser tab that opens once, then say "deploy on DenkOps". Claude packs, builds and ships the current project and hands you back a live URL.
No. The login step is a one-time browser approval, not a token you paste in. Claude Code stores the resulting scoped credential itself, and you can revoke it any time from the dashboard's Connect page.
← Deploy AI agents · Bun+Hono MCP server guide · Express webhook guide