# Let your agent set it up

> One line for your agent; it installs Archee MCP in your client and tells you when to sign in.

Source: https://docs.archee.studio/start/agent-setup

Paste this into Claude Code, Codex, Cursor or any coding agent:

```text
Set up Archee MCP for me by following https://docs.archee.studio/start/agent-setup.md
```

Your agent adds Archee to its own configuration, then asks you to sign in once in the browser. That is the whole setup.

---

## Instructions for the agent

You are setting up Archee MCP for the user. Follow these steps in order, run each command yourself, and stop at the first error to report it.

- **Server name:** `archee`
- **URL:** `https://mcp.archee.studio/mcp` (Streamable HTTP)
- **Sign-in:** OAuth in the browser; the client discovers it from the server. No token is needed unless the user gives you one.

### 1. Find the client you run in

Use the first that applies: you are Claude Code if the `claude` command exists and you are running inside it; Codex if `~/.codex/` exists and you are Codex; Cursor if you are running inside Cursor. If you cannot tell, ask the user which client they use.

### 2. Add the server

Skip this step if a server named `archee` is already configured with the same URL.

**Claude Code.** Add it for every project of this user:

```bash
claude mcp get archee || claude mcp add --transport http --scope user archee https://mcp.archee.studio/mcp
```

**Codex.**

```bash
codex mcp get archee || codex mcp add archee --url https://mcp.archee.studio/mcp
```

**Cursor.** Merge this into `~/.cursor/mcp.json`, keeping every existing server:

```json
{ "mcpServers": { "archee": { "url": "https://mcp.archee.studio/mcp" } } }
```

**Claude Desktop.** It has no configuration file for remote servers. Tell the user: open Settings → Connectors → Add custom connector, name `Archee`, URL `https://mcp.archee.studio/mcp`.

**Any other client.** Add a remote MCP server named `archee` with the URL above, following that client's documentation.

**With a token.** Only if the user gave you a personal access token (`arch_pat_…`): store it in the environment variable `ARCHEE_TOKEN`, never in a file in a repository, and send it as `Authorization: Bearer $ARCHEE_TOKEN` (Claude Code: add `--header "Authorization: Bearer $ARCHEE_TOKEN"`; Codex: add `--bearer-token-env-var ARCHEE_TOKEN`).

### 3. Hand over to the user

Tell the user exactly this, adapted to their client:

- **Claude Code:** "Archee is added. Run `/mcp`, choose `archee` and sign in in the browser."
- **Codex:** "Archee is added. Run `codex mcp login archee` and sign in in the browser."
- **Cursor and others:** "Archee is added. Restart the client; it opens the browser to sign in on first use."

### 4. Check it

After the user has signed in, call the `search` tool with `query="vbelt"`. If it returns function stubs, reply: "Archee MCP is ready." If it fails, use [Troubleshooting](https://docs.archee.studio/mcp/troubleshooting.md) and report the error and its `call_id`.

Do not run `execute` as a test: it is charged in credits.