Skip to main content
Get the Vers CLI installed in under a minute.

Prerequisites

  • Operating System: Linux or macOS
  • SSH Client: Required for connecting to VMs (usually pre-installed)
  • Terminal Access: Command-line interface

Install the CLI

Install the latest version of Vers CLI with a single command:
This script automatically detects your platform and downloads the appropriate binary to /usr/local/bin/vers. You may need administrative privileges for the installation.

Build from Source

If you prefer to build from source:
This installs the binary to /usr/local/bin/vers.

Manual Download

Download the latest release binary from GitHub Releases, make it executable, and move it to somewhere on your PATH:

Verify Installation

Check that Vers is properly installed:
You should see version information like v0.5.1.

Authentication

Get Your API Key

  1. Go to vers.sh and log in
  2. Subscribe to a plan for your organization (if you haven’t already)
  3. Navigate to API Keys in your organization settings
    • Use the org switcher in the top left to select your organization
  4. Create a new API key and copy it

Log In

Paste your API key when prompted. The key is stored locally at ~/.versrc.
You only need to log in once per machine. To see your current API key: cat ~/.versrc

Legacy Installation Cleanup

If you previously had a development version of Vers installed and want to switch to the production version:

Check Your Current Version

If it shows dev instead of a version number like v0.5.1, follow these steps:

Remove the Dev Version

Verify the Switch

Re-authenticate

Add these docs to your AI editor

Vers hosts a Model Context Protocol (MCP) server for this documentation at https://docs.vers.sh/mcp. Tools like Cursor, VS Code, and Claude Code can search and read these pages directly — no scraping, no out-of-date copies.

One-click install

Add to Cursor

Opens Cursor and installs vers-docs as a remote MCP server.

Add to VS Code

Opens VS Code and installs vers-docs into your workspace config.

Other clients

This is separate from vers mcp serve, which exposes the Vers platform as MCP tools (list VMs, exec, branch, etc.). The docs MCP exposes only the docs.

Next Steps

With Vers installed and authenticated, you’re ready to:
  1. Learn the core concepts
  2. Follow the quickstart guide
  3. Explore VM access and SSH

Troubleshooting

Command not found

Make sure /usr/local/bin is in your $PATH:
If it’s not included, add it to your shell configuration (~/.bashrc, ~/.zshrc, etc.):

Authentication issues

  • Verify your API key is correct
  • Check that you have an active subscription at vers.sh
  • Try logging out and back in: vers logout && vers login

Installation script fails

Try one of these alternatives:

What’s next

Quickstart

Boot your first VM and take your first branch in ~10 minutes.

Core concepts

The mental model: projects, VMs, HEAD, branches, commits.

Configuration

Memory, vCPUs, disk, kernel — every vers.toml field.

VM access

SSH, exec, and file-transfer patterns.