Install paths

There are two ways to bring an agent online with AgentValet today, and a third in development. Pick the one that matches how the agent runs.

MCPB (Claude Desktop, Claude Code)

The MCPB is a single-file extension bundle that installs into Claude Desktop. You download agentvalet-latest.mcpb from agentvalet.ai/install , drag it into Claude’s extensions window (or install it via Settings → Extensions → Advanced settings → Install extension on Windows 11 Store builds), and Claude can now call AgentValet tools.

Best for:

• Claude Desktop users wanting governed access to their platforms
• Personal automations where the agent runs on your machine
• Non-developers — the install is GUI-only

CLI

The CLI is npx @agentvalet/register. Run it in your project root; it walks you through:

1. Sign in (browser pops to Clerk; CLI receives a session token via /cli-auth)
2. Generate an RS256 keypair, register the agent under your account
3. Write the private key to ~/.agentvalet/agent.key (0600) and project-level configs for whatever IDE/framework it detects
4. Wait for you to approve the registration in the dashboard

It detects and writes config for: Claude Code, Cursor, Codex, OpenClaw, Factory Droid. After registration you have a working .mcp.json (or equivalent) wired up to your new agent.

Available subcommands:

• (no args) — interactive registration wizard
• refresh — pull the latest granted-permissions list into .claude/agentvalet-permissions.md
• mcp-server — run the MCP server over stdio (for IDEs that launch it themselves)
• list — list locally-configured agents
• revoke — revoke an agent
• inject — write env vars to a file for shell injection
• uninstall — remove local config

Best for:

• Developers integrating AgentValet into a codebase
• Headless agents (servers, CI jobs, cron) where you need env-var injection
• Multi-environment setups (one agent per env, each with its own key)

Invite (coming soon)

A planned third path: a manager invites a teammate by email, the teammate clicks a link to claim, installs MCPB or runs the CLI, and the agent self-binds to the manager’s pre-configured scopes. No back-and-forth, no copy-pasting owner IDs.

The design is documented in docs/roadmap/invite-flow.md. It’s not shipped yet — when it is, this page will have a third section.

Picking between MCPB and CLI

Both paths converge — once registered, an agent is an agent. The difference is purely how the keypair gets generated and where it ends up living on disk.

Next

• Get started in 5 minutes
• Register via the CLI