Skip to main content

Linux installation

AgentDock provides precompiled binaries for Linux x64 and ARM64.

The default flow below allows local access only, suitable for initial setup and server deployments.

1. Install​

Run in terminal:

curl -fsSL https://github.com/uvwt/agentdock/releases/latest/download/install.sh \
  -o /tmp/install-agentdock.sh
sudo sh /tmp/install-agentdock.sh

The installer automatically detects systemd or OpenRC, creates a low-privilege runtime user, generates a Bearer Token, starts the service, and verifies health.

2. Verify service​

systemd:

sudo systemctl status agentdock --no-pager
curl -fsS http://127.0.0.1:8765/healthz

OpenRC:

sudo rc-service agentdock status
curl -fsS http://127.0.0.1:8765/healthz

A healthy response contains "ok": true.

3. View Bearer Token​

sudo awk -F= '/^AGENTDOCK_AUTH_TOKEN=/{print $2}' \
  /etc/agentdock/agentdock.env

Save the token in your password manager. Do not include it in Git, screenshots, or public chats.

4. Connect MCP client​

When the client is on the same Linux machine, enter:

Transport    Streamable HTTP
URL          http://127.0.0.1:8765/mcp
Headers      Authorization: Bearer <your token>

When AgentDock runs on a remote server, establish an SSH tunnel from your computer:

ssh -L 8765:127.0.0.1:8765 <username>@<server-address>

Keep the SSH session open, then connect your local client to http://127.0.0.1:8765/mcp.

tip

Setup complete: once the service is running, health checks pass, and the MCP URL and token are added to your client.

Optional: Create public address​

The default installation allows local access only. When connecting from ChatGPT, mobile devices, or other remote clients, rerun interactive installation:

sudo sh /tmp/install-agentdock.sh

The installer asks if you have a Cloudflare-managed domain:

  • No domain: automatically creates a temporary trycloudflare.com address for quick testing.
  • Have a domain: complete the Public access, then enter the resulting HTTPS public origin and Tunnel Token when the installer asks.

After installation, the terminal displays the public MCP URL and connection credentials. A temporary address may change after a restart. Generate a new one with sudo /opt/agentdock/bin/agentdock tunnel regenerate --runtime-root /etc/agentdock, then replace the old MCP URL in the client and authorize OAuth again. Existing Bearer Token and OAuth credentials are preserved.

Public access requires authentication. For detailed parameters and log locations, see Public access.

Update​

Check first, then install the latest release:

sudo /opt/agentdock/bin/agentdock update --check
sudo /opt/agentdock/bin/agentdock update

Tasks, Skills, configuration, and working directories are preserved. Rerun the installer only when you need to repair the installation or install a specific version.

Next steps​

  • For browser automation: install Chrome, Chromium, or Microsoft Edge on the host and enable browser tools; set AGENTDOCK_BROWSER_EXECUTABLE_PATH if not detected automatically. Docker browser images are needed only when you want Chromium contained in Docker. See Browser automation.
  • For Alpine, custom directories/ports, manual service management, and uninstallation: see Linux and servers.
  • For manual systemd, reverse proxy, and OAuth maintenance: see Linux and servers.
  • If startup fails: see Troubleshooting.
  • For public access: see Public access.