Operator guide for Valet Dedicated 0.10.1

Connect your people

Install ends with one superuser. This page connects everyone else: their network, their sign-in, and the tools they use. Finish Install first.

1. Give people network access

The installation's hosts answer only inside your VPC, or over a network path you provide. Every person needs that path: your VPN, or your office network. See Install.

Check from a person's machine:

curl -sS https://api.<apex>/health

You see a response from the API. If the name does not resolve, the machine's resolver does not forward the apex to the VPC. If the request times out, the machine has no route to the VPC.

2. Sign in once

Each person opens https://dashboard.<apex> and signs in through WorkOS. The first sign-in adds the person to the home org as a Developer. Tools that sign in later find the person already in the org.

3. Connect a tool

Replace <apex> with your apex in every command below.

Claude Code

claude mcp add --transport http valet https://api.<apex>/mcp

Start Claude Code, run /mcp, and choose valet. A browser opens. Sign in through WorkOS.

You see valet listed as connected.

Codex

Add the server:

codex mcp add valet --url https://api.<apex>/mcp

Then sign in:

codex mcp login valet

You see a browser open for WorkOS sign-in, then a success message.

Other MCP clients

Add an HTTP (streamable) MCP server with the URL https://api.<apex>/mcp. The client signs in with OAuth.

The valet CLI

Install the CLI on a machine with network access:

curl -fsSL https://www.valet.dev/install.sh | sh

Set three variables. The client ID is the one Valet sent you in Prepare.

export VALET_API_URL=https://api.<apex>
export VALET_GATEWAY_URL=https://gateway.<apex>
export VALET_WORKOS_CLIENT_ID=<client ID>

Add them to your shell profile so every shell has them. Then sign in:

valet auth login

A browser opens. Sign in through WorkOS. You see a confirmation in the terminal.

Connect private servers

For a private MCP server or model gateway, configure network.private_destinations. Provide a route from the installation's VPC through peering, Transit Gateway, or a VPN, and DNS resolution for its name. Only platform services dial the listed destinations. Runtime and builder workloads gain no network access.

Hosted clients do not connect

claude.ai, ChatGPT, and the Claude Desktop connector gallery call your installation from their vendor's cloud. The cloud cannot reach an internal load balancer. See Limits and known gaps.

Next

Read Limits and known gaps before you plan your first rollout.