Set up Claude Desktop

Claude Desktop launches local MCP servers from its config file. The hosted server is remote, so the config runs the mcp-remote bridge — a small local process that forwards to mcp.hypervalent.io with your token. You need Node.js 18 or newer installed.

Why not add it as a Connector?

Claude Desktop's Connectors screen accepts remote servers, but it cannot send a custom Authorization header, and the Hypervalent server authenticates with your API token in that header. The bridge adds it. Claude Code and Cursor talk to the hosted URL directly.

1. Get the snippet from Studio

In Studio open Settings → API tokens, create a Read + write token if you want the assistant to author content (which token?), then open the Use with AI panel, choose Claude Desktop and copy the snippet.

The snippet shows the token's prefix followed by …, never the full token — Studio shows a token exactly once, when it is created. Replace the placeholder with the full atk_… value.

2. Edit the config file

Open the file from Claude Desktop itself: Settings → Developer → Edit Config. That opens the folder and creates the file if it does not exist.

Platform	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

If the file is empty, the snippet is the whole file. If it already has an mcpServers block, add the hypervalent entry beside the existing ones:

json

{
  "mcpServers": {
    "hypervalent": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.hypervalent.io/mcp?org=YOUR_ORG_ID",
        "--header", "Authorization: Bearer atk_YOUR_TOKEN"
      ]
    }
  }
}

Node installed with nvm, Volta or asdf?

Claude Desktop starts with a minimal system PATH and will not find a version-managed npx. Use the absolute path instead — the output of which npx in a terminal, for example /Users/you/.nvm/versions/node/v22.14.0/bin/npx — as the command value. The symptom otherwise is the server showing as failed straight after launch.

3. Restart Claude Desktop

Quit fully (⌘Q on macOS — closing the window is not enough) and relaunch. The config is read only at startup.

4. Check it connected

Open Settings → Developer. hypervalent should show as running. In a new chat the tools icon lists the Hypervalent tools; ask:

Which Hypervalent projects can you reach?

The assistant calls list_projects and names your project(s).

If the server shows failed, the log is at ~/Library/Logs/Claude/mcp-server-hypervalent.log (macOS) — the last lines usually name the cause. The troubleshooting page lists the common ones.

Approving tool calls

Claude Desktop asks before the first use of each tool in a chat and offers "allow for this chat". Writes that affect live sites — publish, unpublish, trash — are annotated as such, and it is worth leaving those on ask-every-time.

Set up Claude Desktop ​

1. Get the snippet from Studio ​

2. Edit the config file ​

3. Restart Claude Desktop ​

4. Check it connected ​