> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ezforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Deploy your first MCP server in 5 minutes

<Note>
  The `ezforge` CLI is currently at `v0.1.0` (pre-GA). Commands and flags may change before `v1.0.0`.
</Note>

## Prerequisites

* An ezForge account ([sign up free](https://app.ezforge.ai/auth/signup))
* Docker installed (for building container images)
* Node.js 20+ or Python 3.11+ (if using a template)

## Step 1: Install the CLI

<Tabs>
  <Tab title="Homebrew (macOS / Linux)">
    ```bash theme={null}
    brew install ezforgeai/tap/ezforge
    ```
  </Tab>

  <Tab title="Download binary">
    Download the latest pre-built binary for your platform from [GitHub Releases](https://github.com/ezforgeai/ezforge-cli/releases/latest). Available platforms:

    * macOS (Apple Silicon): `ezforge_<version>_darwin_arm64.tar.gz`
    * macOS (Intel): `ezforge_<version>_darwin_amd64.tar.gz`
    * Linux (x86\_64): `ezforge_<version>_linux_amd64.tar.gz`
    * Linux (arm64): `ezforge_<version>_linux_arm64.tar.gz`
    * Windows (x86\_64): `ezforge_<version>_windows_amd64.zip`
    * Windows (arm64): `ezforge_<version>_windows_arm64.zip`

    **macOS / Linux** — replace `<os>_<arch>` with your platform (e.g. `darwin_arm64` for macOS Apple Silicon, `linux_amd64` for Linux x86\_64), then extract and move to a directory in your `$PATH`:

    ```bash theme={null}
    tar xzf ezforge_<version>_<os>_<arch>.tar.gz
    sudo mv ezforge /usr/local/bin/
    ```

    **Windows** — in PowerShell: `Expand-Archive ezforge_*_windows_*.zip -DestinationPath .` then move `ezforge.exe` to a directory in your `$PATH`.

    Verify the SHA-256 of your download against `checksums.txt` attached to the release.
  </Tab>
</Tabs>

Verify the install:

```bash theme={null}
ezforge --version
```

## Step 2: Authenticate

```bash theme={null}
ezforge auth login
```

This opens your browser to complete the OAuth flow. Your credentials are saved locally and used for all subsequent commands.

## Step 3: Create a project

```bash theme={null}
ezforge project create my-first-project
```

Projects are workspaces that group servers, API keys, and billing together.

## Step 4: Clone the Node.js template

```bash theme={null}
git clone https://github.com/ezforgeai/template-nodejs-mcp-server my-mcp-server
cd my-mcp-server
npm install
```

The template includes two sample tools out of the box:

* **`echo`** — returns whatever message you send it
* **`add`** — adds two numbers and returns the result

## Step 5: Deploy

```bash theme={null}
ezforge deploy
```

ezForge will:

1. Build your container image
2. Scan it for vulnerabilities with Trivy
3. Push it to the registry
4. Provision a Firecracker microVM
5. Run a health check at `GET /healthz`
6. Swap traffic to the new deployment

Output:

```
✓ Building image...
✓ Scanning image (0 critical, 0 high)
✓ Pushing to registry...
✓ Provisioning machine in ord...
✓ Health check passed
✓ Deployed!

Your server is live at: https://my-mcp-server.mcp.ezforge.ai
```

## Step 6: Test your server

Connect to your live server from any MCP client:

```
https://my-mcp-server.mcp.ezforge.ai/sse
```

Or test the health check directly:

```bash theme={null}
curl https://my-mcp-server.mcp.ezforge.ai/healthz
# {"status":"ok"}
```

## What's next?

<CardGroup cols={2}>
  <Card title="Add authentication" icon="lock" href="/getting-started/authentication">
    Protect your server with OAuth 2.1
  </Card>

  <Card title="Node.js template guide" icon="js" href="/templates/nodejs">
    Add your own MCP tools to the template
  </Card>

  <Card title="Python template guide" icon="python" href="/templates/python">
    Deploy a Python-based MCP server
  </Card>

  <Card title="CLI reference" icon="terminal" href="/cli-reference/overview">
    Full CLI command reference
  </Card>
</CardGroup>