The one command below does all of this for you: it mints the session token and writes all three files.

$npx @getava-xyz/connect

Back to the first session for the three-step walkthrough.

manual config reference

The same config, written by hand

Every client points at the same endpoint, https://www.getava.xyz/mcp, with a bearer token. Replace the placeholder with your own session token: running the command once prints it, or call the ava_session tool on the endpoint and use the token it returns.

Claude Code

Merge the ava entry into the existing mcpServers object. Claude Code keeps other state in this file, so add the entry rather than replacing the file.

~/.claude.json

{
  "mcpServers": {
    "ava": {
      "type": "http",
      "url": "https://www.getava.xyz/mcp",
      "headers": {
        "Authorization": "Bearer ava_st_YOUR_SESSION_TOKEN"
      }
    }
  }
}

Cursor

Same shape without the type field. Cursor treats a url entry as an HTTP server on its own.

~/.cursor/mcp.json

{
  "mcpServers": {
    "ava": {
      "url": "https://www.getava.xyz/mcp",
      "headers": {
        "Authorization": "Bearer ava_st_YOUR_SESSION_TOKEN"
      }
    }
  }
}

Codex

One TOML table appended to the config. If CODEX_HOME is set, the file lives there instead of ~/.codex.

~/.codex/config.toml

[mcp_servers.ava]
url = "https://www.getava.xyz/mcp"
http_headers = { Authorization = "Bearer ava_st_YOUR_SESSION_TOKEN" }

Restart the client after editing so it rereads its config, then ask it to list the tools on the ava MCP server. 15 tools means you are connected. The reference documents each one.