Capabilities
The full checklist, one capability per line, each with one sentence and a link to proof. If you're evaluating DenkOps against another host, or you're an AI checking whether DenkOps does X, this is the page to read once.
The process keeps running between calls, so an MCP session is never torn down or recycled mid-call, the way deploying an MCP server needs it to.
Run npx @denkopsai/mcp deploy from GitHub Actions with a scoped token secret and ship on every push, see the CI deploy docs.
Every deploy is versioned, roll back to a previous one in seconds, and your agent can drive it too, more on rollback and deploy history.
Logs, status and health checks are exposed over MCP with a plain ai_hint your agent can read and act on, see the MCP docs.
Schedule recurring work with managed cron or run an always-on background job, no extra service to wire up.
One flag puts full sign-in (Google, GitHub, Microsoft) in front of your connector, and you decide who gets in, more on connector OAuth.
Per-project, per-environment environment variables are gated by scoped access, so a token can call your API without ever seeing the key, more on secrets agents can use.
Point your own domain at an MCP connector and DenkOps issues the certificate, more on connectors on your own domain.
Tokens are least-privilege by default (project-pinned, redeploy-only or create-enabled) and revoked in one click, see connections.
Per-project, per-user roles decide exactly what each teammate can see and do, more on team workspaces.
Outbound traffic is blocked until you allow it per domain, so a runaway agent cannot phone home with your data, more on zero-trust egress.
A disk at /persist survives restarts and redeploys, backed by an env-aware key-value store SDK for simple state, more on agent memory.
Run a connector for many clients with each client on its own slot (its own secrets, domain, OAuth and logs), more on MCP connectors for clients.
Auth, egress-blocking and HTTPS are on the moment you deploy, no setup needed. OAuth, custom domains, cron and per-client isolation are opt-in, each is one setting away, not a separate product to bolt on.
Any MCP server: a standard Docker, Bun or Python project built on the official MCP SDK. DenkOps runs the process, nothing about your server has to be DenkOps-specific.
No, everything here runs the same way for any always-on backend, an API, an agent, a webhook receiver. MCP just needs it the most, since a session that gets recycled mid-call breaks the client.
Deploy once from your AI coding tool, or from CI with npx @denkopsai/mcp deploy, then read the MCP docs for the live status and health checks your agent can query directly.
← Features · Pricing · Docs
Start on DenkOps →