# CVRevise agent access: setup guide (kit 1.1.0)

For AI agents and their owners. Replace <KEY> with the owner's CVRevise agent key (it starts with cvrk_). The owner can
give the key to the AI, or run the commands himself.

## 0. Before you start
1. The owner creates a key at https://cvrevise.com/account/agents. That page also gives a ready setup message for the AI.
2. Find out which harness you run in: Hermes (section 1), Claude Code (2), Codex (3), another MCP app (4).

## 1. Hermes
Run these two commands (the AI with its terminal tool, or the owner):
    hermes config set mcp_servers.cvrevise.url "https://cvrevise.com/mcp"
    hermes config set mcp_servers.cvrevise.headers.Authorization "Bearer <KEY>"
If Hermes refuses an unknown key, repeat the command with --force.
Use these commands, not file edits: a Hermes agent cannot write the Hermes .env file and cannot read config.yaml with its
file tools.
A running session reloads MCP servers when config.yaml changes; otherwise run /reload-mcp or start a new session.
Check: hermes mcp test cvrevise. Tools appear as mcp_cvrevise_<tool>.
Owner alternative in a terminal (asks for the key and keeps it in .env):
    hermes mcp add cvrevise --url https://cvrevise.com/mcp --auth header
Skill (optional; install it if the owner agrees):
    hermes skills install https://cvrevise.com/agent-kit/cvrevise/SKILL.md
Optional: setting this server's trust to untrusted makes Hermes ask before every tool that is not read-only.

## 2. Claude Code
Run this command (the AI with its shell tool, or the owner in a terminal):
    claude mcp add --transport http --scope user cvrevise https://cvrevise.com/mcp --header "Authorization: Bearer <KEY>"
Then start a new Claude Code session. Check: claude mcp get cvrevise
Skill (optional; install it if the owner agrees; on Windows the folder is %USERPROFILE%\.claude\skills\cvrevise):
    mkdir -p ~/.claude/skills/cvrevise
    curl -fsSL https://cvrevise.com/agent-kit/cvrevise/SKILL.md -o ~/.claude/skills/cvrevise/SKILL.md
Optional: the permission allow rule mcp__cvrevise__* lets CVRevise tools run without a prompt each time.

## 3. Codex
Add this block to ~/.codex/config.toml (the AI with a file edit, or the owner):
    [mcp_servers.cvrevise]
    url = "https://cvrevise.com/mcp"
    http_headers = { "Authorization" = "Bearer <KEY>" }
Then start a new Codex session. Check: codex mcp list
Codex may ask the owner before writing outside the workspace or using the network; that is expected here.
Skill (optional; install it if the owner agrees; on Windows the folder is %USERPROFILE%\.agents\skills\cvrevise):
    mkdir -p ~/.agents/skills/cvrevise
    curl -fsSL https://cvrevise.com/agent-kit/cvrevise/SKILL.md -o ~/.agents/skills/cvrevise/SKILL.md
Approvals: Codex always asks before tools marked destructive. To be asked before every write, add
default_tools_approval_mode = "writes" inside the same block. Do not use a plugin-bundled MCP entry for this server
(Codex drops the Authorization header there).

## 4. Other MCP apps (not certified)
Any app that supports remote Streamable HTTP servers with a custom header: URL https://cvrevise.com/mcp, header
Authorization: Bearer <KEY>.

## 5. Verify
Call whoami. Expect the owner's name, the wallet balance, the key's limits and the kit version. invalid_token means the
key is missing, revoked or expired.

## 6. Remove
- Hermes: hermes mcp remove cvrevise.
- Claude Code: claude mcp remove cvrevise --scope user.
- Codex: codex mcp remove cvrevise, or delete the [mcp_servers.cvrevise] block from ~/.codex/config.toml.
- Then revoke the key at https://cvrevise.com/account/agents.