My connection

See how your assistant connects to Dokploy Unleashed, what a connection can and cannot do, and how to disconnect. A connection acts on exactly one Dokploy instance — yours — using your own Dokploy API key. There is no shared or host key for anyone to inherit.

Connect ChatGPT or Claude (OAuth sign-in)

In the app, add a custom connector and give it the server URL: https://dokploy.robinsonaisystems.com/mcp
The app opens this service's own sign-in page, "Connect your Dokploy". Enter your own public HTTPS Dokploy URL and your own Dokploy API key there — the key goes to this service only; the app never sees it and receives an OAuth token instead.
Your key is checked against your Dokploy instance before anything is stored, then encrypted at rest (AES-256-GCM) in a dedicated tenant database. OAuth tokens are stored only as hashes.
Done. The app reconnects by itself when its token expires; removing the connector in the app disconnects it.

Connect a key-based client (direct API-key sign-in)

Clients that cannot complete the OAuth flow may present your own Dokploy API key on every request instead:

POST https://dokploy.robinsonaisystems.com/mcp
Authorization: Bearer <your Dokploy API key>
X-Dokploy-Instance: <your public HTTPS Dokploy origin>

The key is validated against your instance before anything is served, and nothing is stored or logged for these sessions. Keep the key in your platform's secure credential store — a secrets manager, an OS keychain, a connector credential page.

Your key stays yours

You never type your Dokploy API key into a chat message, a random web page, or a file someone sent you. A Dokploy API key is entered in exactly two kinds of places: this service's own sign-in page on this address, and your own platform's protected credential setup. Whoever holds your key can act on your Dokploy with its permissions — treat it that way.

One honest note: this service is not zero-knowledge hosting. Robinson AI Systems operates the encryption and can technically decrypt stored keys to run the service. Only connect Dokploy instances you control, and only if you trust the operator to process these credentials. How credentials are handled.

What a connection can and cannot do

Can: discover, inspect and run the documented Dokploy operations on your instance — reads and writes alike — to exactly the extent your own API key allows. This gateway adds no permission tier, write switch or approval system of its own; your AI host may still ask you before destructive actions.
Cannot: reach anyone else's Dokploy instance, use another user's key, or exceed your key's Dokploy permissions. Dokploy itself enforces what your key may do.
Your instance must be reachable by public HTTPS. Private, loopback and internal addresses are rejected, to keep one user's connection from ever pointing at someone else's network.

Disconnect

For OAuth connections, the dokploy_disconnect tool deletes your stored API key and revokes every session for your connection; removing the connector in your app also ends its access. For direct-key sessions, remove the key from your client or rotate it in Dokploy. Revoking the API key inside Dokploy stops it working everywhere, immediately.

← Dokploy Unleashed home

Dokploy Unleashed is an independent service by Robinson AI Systems and is not affiliated with or endorsed by Dokploy. Availability, features and tools can change at any time, and Dokploy can change or limit the service this tool works through — this page describes things as they stand today, not a promise about tomorrow. Dokploy Unleashed works through your own Dokploy instance, with your own API key, and Dokploy's own terms govern that instance.