Docs · Connector

DenkOps in your AI assistant.

Add one URL, https://denkops.com/mcp, as a connector in Claude, ChatGPT, Gemini or Grok. Sign in with Google or GitHub (a DenkOps account and workspace are created on your first sign-in), then ask your assistant to build, deploy and run APIs, MCP servers and scheduled jobs.

What it can do

• Deploy a project: the assistant writes the files and sends them; you get a live HTTPS URL and an API key.
• Manage projects and slots: status, start, stop, redeploy, roll back, delete (with an explicit confirmation).
• Debug: container logs, request traces and metrics.
• Configure: environment variables (write-only), public paths, egress allow-list, custom domains, scheduled jobs.
• Plan and slots: see how many slots are used and free, and get a one-click Stripe link to subscribe or add slots (workspace owners; other members are told which owner to ask).
• Connections: list, create and revoke scoped tokens, e.g. for GitHub Actions deploys (workspace owners).
• Guidance: the connector explains the DenkOps project layout (denkops.json, bun + Hono, python + FastAPI, MCP servers) to the assistant.

Add the connector

Claude (claude.ai, Desktop, mobile)

Settings → Connectors → Add custom connector. Name it DenkOps, URL https://denkops.com/mcp. Authentication: Sign in now, or Sign in when needed to connect first and sign in on the first action. OAuth client: Use Claude's published identity (or Register automatically). In Claude Code: claude mcp add --transport http denkops https://denkops.com/mcp, then run /mcp to sign in.

ChatGPT

Open the DenkOps app in the ChatGPT app directory and connect. Until it is listed: Settings → Apps & Connectors → Advanced → Developer mode, then Create with URL https://denkops.com/mcp and OAuth authentication.

Gemini

In the Gemini app, add a custom app / connected app with the MCP URL https://denkops.com/mcp. In Gemini CLI: gemini extensions install https://github.com/DenkOpsAI/denkops-mcp.

Grok

grok.com → Connectors → New connector → Custom, URL https://denkops.com/mcp. Through the xAI API, declare the same URL as a remote MCP tool.

Any other MCP client

It is a standard remote MCP server (Streamable HTTP, protocol 2026-07-28 and the 2025 revisions) with OAuth 2.1: PKCE, dynamic client registration and client ID metadata documents. Discovery starts at https://denkops.com/.well-known/oauth-protected-resource/mcp.

Sign-in and permissions

Before you sign in, the assistant can already see the tools and read the DenkOps build guide; the first action on your account (listing projects, deploying, …) asks you to sign in. You sign in with Google or GitHub. If you belong to several workspaces you pick one on the consent screen. The connector then acts as you in that workspace: your role (owner, member or viewer) and any per-project access rules apply exactly as in the dashboard. Access tokens last one hour and are refreshed automatically; if you leave the workspace or your account is disabled, the connection stops working immediately.

Secrets never travel in deploy uploads: .env files are refused and environment variables are set separately, stored encrypted and never shown back.

Disconnect

Remove the connector in your assistant's settings, and/or revoke it in the DenkOps dashboard under Connections. Revoking takes effect right away.

Privacy, terms and support

See the privacy policy and terms. Questions or problems: ops@denkops.com. Security reports: security.