Docs

How to connect a server, work on it through ChatGPT, and keep track of what happened.

Getting started

1. Add a server. From Servers, enter a name, its hostname and port, the SSH username Gateway should use, and a region. Leave the region on automatic unless you have a reason not to.
2. Connect it. Give Gateway the server's password and it completes the setup for you. If you'd rather not, see setting up without a password.
3. Start working. Once setup finishes, the server is ready to use from ChatGPT.

Servers

Setting up without a password

You don't have to give Gateway a password. Leave the field blank and Gateway gives you a key to install yourself, on the server's SSH identity tab. Add it to the authorized_keys file for the account Gateway will use, however you normally would: your provider's console, cloud-init, or by hand.

You can also add a server before you know its address. Gateway gives you the key straight away, you install it, and you fill in the hostname and username afterwards. The server keeps its name and history throughout.

Managing and removing servers

The SSH identity tab is also where you replace the access Gateway uses, or take it away. Replace it if you think the current access shouldn't be trusted any more; you'll need to install the new key if you set the server up without a password.

Deleting a server removes it from Gateway and revokes the access Gateway held for it. Your record of what happened on it stays in Activity. Both actions ask you to confirm who you are first.

Changing region

You can move a server to a different region if you'd rather Gateway connected from somewhere else. Each region lists the addresses Gateway connects from, so you can allow them through your firewall.

Using ChatGPT

Once a server is ready, just ask. ChatGPT can look into services, containers, packages, files, networking, storage, users, and general system health, and it can make changes as well as read state.

• "Why is web-01 returning 502s?"
• "Restart the app service on web-01 and confirm it came back."
• "What's filling up the disk on db-02?"
• "Are there security updates pending on any of my servers?"
• "Pull the last 200 lines of the nginx error log."

Application-specific and unusual work is fine too.

Using Claude

Gateway works the same way in Claude. In Claude, open Settings, then Connectors, choose Add custom connector, and enter https://trygateway.sh/mcp. Sign in to Gateway when Claude asks, approve access, and you're back in Claude, ready to ask.

In Claude Code, run claude mcp add --transport http gateway https://trygateway.sh/mcp, then sign in from /mcp.

Claude never needs your passwords. If a job needs sudo, Claude gives you a link to Gateway, where you choose to allow it just this once, for a while, or always. If a job needs a token, you type it into Gateway once and Claude refers to it only by name. You can see and revoke Claude's access from your Gateway account at any time.

Files and history

Files

You can pull files off a server and download them from Files, and copy files between two servers you've connected. Files are only ever available to your own account.

Jobs

Jobs shows work on your servers as it runs and after it finishes, with its output and result. Work started by an AI assistant is labelled with its name, such as ChatGPT or Claude, so you can tell it apart from anything you ran yourself. Filter by server, and cancel anything still running.

Activity

Activity is the longer record: sign-ins, servers added and removed, access changes, and billing events. Each server has its own Activity tab too, if you only care about one of them.

Account and billing

Settings, then Billing, is where you upgrade, downgrade, or cancel. Downgrading never deletes a server. It only stops you adding new ones past your new limit. See pricing for what each plan includes.

Sign-in methods is where you add or remove ways of getting into your account. Link a second one so you have a fallback. If you lose access to all of them, contact support. Once we verify account ownership, we can issue a one-time login code so you can regain access and add a new passkey.

Troubleshooting

• Setup fails. Check the hostname, port, and username, and that the server is reachable. Each region lists the addresses Gateway connects from, so you can allow them through your firewall.
• The password wasn't accepted. Confirm the account can log in with it over SSH. If password setup still doesn't work, you can install the SSH key yourself.
• A server stopped working after a rebuild. Rebuilding usually changes the server's identity, so Gateway stops trusting it on purpose. Confirm it really is your server, then re-establish trust from the server's page.
• Work is taking a long time. Long jobs keep running and stream output as they go. You can cancel from Jobs at any point.
• You can't add another server. You've reached your plan's limit.

Things to know

• Job output is kept for seven days. Your Activity history is a longer-term record and remains available after a server is removed.
• If you lose access to every linked sign-in method, contact support. Once we verify account ownership, we can issue a one-time login code so you can regain access and add a new passkey.