Register — MCP Terminal Server

Step 1 — Your VPS

Point us at a fresh Ubuntu LTS VPS (22.04 / 24.04 / 26.04) and pick a project name.

Host (IP or DNS name) Project name

_…

We'll create user … on your VPS.

Naming rules & details

Host: an IPv4 like 95.216.192.251 or a DNS name like prod.example.com — no port, no brackets.

Project name: 2–30 lowercase letters, digits, _ or -, starting with a letter or _. The suffix is the dashed host. root, admin and similar reserved names are refused.

Everything we install (CLIs, MCP proxy, project sandbox) lives under that user.

Step 2 — Run one command on your VM

SSH into your VPS as root, paste the command below, and press Enter.

Open an SSH session as root:
ssh root@—
Copy this command, paste it, press Enter:
—

What does this command do?

It creates the Linux user user, installs a fresh SSH key into their ~/.ssh/authorized_keys, and writes a narrow NOPASSWD sudoers entry the provisioner needs. Run it as root on a fresh VPS — a non-root shell skips the sudoers part and preflight will refuse.

The key is wrapped in authorized_keys options so sshd refuses anything we don't need:

That user owns everything we install (CLIs, MCP proxy, project sandbox) — a separate, project-scoped identity. For a hard sandbox use an authorized_keys command="…" wrapper on your end.

Waiting for your VM…

How does this work?

We try an SSH probe every 3 seconds. As soon as it connects, we provision your account automatically.

0s elapsed

Step 3 — You're registered

Your account is being activated. The browser will be ready in a few seconds.

Sign in as

—

Password

—

About these credentials

Sign-in name = project label + dashed host (<project>_<host>), the same identifier as the Linux user on your VPS. The password is a random 24-character string — copy it verbatim, the +// characters are part of it.

The Sign-in button activates your account and takes you straight to provisioning. It may pause a second or two — your password is set up the instant after registration, and we wait for it to go live before letting you in (no need to retype anything).

SSH line we installed (reference)

Already in place — kept here in case you re-add it after a server rebuild or copy this identity onto a second target.

—

Step 3 — Registration failed

—