DenkOps now works as a connector inside the assistants you already use. Add one URL, https://denkops.com/mcp, to Claude, ChatGPT, Gemini, Grok, Claude Code or Cursor, sign in with Google or GitHub, and your assistant can deploy an API, read its logs, roll back a bad release or set a secret, without you opening a terminal or a dashboard.
What changed?
Until now, DenkOps was driven from coding agents through a local MCP server that you installed and paired. That still works. What is new is a hosted connector: a remote MCP server with its own OAuth sign-in, so any assistant that supports remote connectors can use DenkOps by URL.
- No install. It is a URL, not a package.
- No token to copy. You sign in on DenkOps' own page with Google or GitHub; the assistant receives a short-lived token for the workspace you approve.
- No account first. Your first sign-in creates your DenkOps account and a workspace with a free slot.
Setup guides for every assistant live on denkops.com/connect: Claude, ChatGPT, Gemini, Grok, Claude Code, Cursor and any other MCP client.
What can the assistant do?
Everything you do day to day:
- Ship. Ask "deploy this API on DenkOps". The assistant writes the files and sends them in the deploy call; you get a live HTTPS URL and an API key.
- Operate. Status, container logs, request traces, latency and error rates, rollback, start, stop, redeploy.
- Configure. Environment variables, custom domains, public paths, the egress allow-list and scheduled jobs.
- Plan. See how many slots you use. When they run out, the assistant hands you a one-click Stripe link for your workspace; nothing is charged until you confirm on Stripe.
The assistant also reads the DenkOps build guide through the connector, so it knows the project layout and denkops.json before it writes a line of code.
Is it safe to let an assistant deploy?
The connector acts as you. Your workspace role and per-project permissions apply exactly as in the dashboard, and the connection stops the moment you leave the workspace or revoke it.
- Access tokens last one hour and refresh automatically; you can revoke a connection any time.
- Secrets never travel in uploads.
.envfiles are refused; environment variables are stored encrypted and are write-only. - Destructive tools (delete, stop, rollback) are marked as such, so assistants ask before running them, and deleting a project needs its exact slug.
- You can connect first and sign in later: with "sign in when needed", listing tools and reading the guide work before you sign in, and your first real action starts the sign-in.
How do I try it?
Open denkops.com/connect, pick your assistant and follow the three or four steps. Then ask: "which DenkOps projects do I have?" On a new account the answer is none yet. Ask it to deploy a tiny API and you will have a live URL a minute later.