Agent integrations

Available integrations

• Claude Code: available
• Codex: available
• Cursor: available
• ChatGPT app: coming later through Semavora account sign-in (OAuth). This is separate from Codex, which works with a key now

Create an agent key

In the portal, open Workspace settings → Agent access (admins only) and create a key. Choose Read and run audits and checks if your agent should start audits and fix checks, or Read only. Copy the key: it is shown once.

Claude Code

Run this command in PowerShell or a macOS/Linux terminal. Replace smv_YOUR_KEY with your saved key:

claude mcp add --scope user --transport http semavora https://mcp.semavora.com/mcp --header "Authorization: Bearer smv_YOUR_KEY"

User scope makes the connection available in all your projects. Start a new Claude Code session, then run /mcp and confirm Semavora is connected.

If an earlier connection was added only for the current folder, remove that entry first: claude mcp remove semavora --scope local. Keep your key private and out of Git.

Codex

The Codex CLI, IDE extension and desktop app use your personal configuration. Open C:\Users\<you>\.codex\config.toml on Windows, or ~/.codex/config.toml on macOS/Linux. Add:

[mcp_servers.semavora]
url = "https://mcp.semavora.com/mcp"
bearer_token_env_var = "SEMAVORA_API_KEY"

Windows PowerShell

Save the key in your Windows user environment before starting Codex:

[Environment]::SetEnvironmentVariable("SEMAVORA_API_KEY", "smv_YOUR_KEY", "User")

Fully quit and reopen Codex, and any terminal or IDE that launches it. Starting a new chat in the same app does not reload the environment. For an immediate CLI test from this PowerShell window:

$env:SEMAVORA_API_KEY = "smv_YOUR_KEY"
codex

macOS / Linux

Set the key, then launch Codex from the same terminal:

export SEMAVORA_API_KEY="smv_YOUR_KEY"
codex

For later terminal sessions, set the variable privately in your shell profile. A GUI app launched outside that terminal may not inherit the variable; launch it from the configured environment or configure its launcher. Keep keys out of repository files. Use codex mcp list to check the configured server, then ask Codex to call Semavora.

Official Codex MCP documentation

Cursor

In your personal ~/.cursor/mcp.json, use an environment reference rather than storing the key in a project file:

{
  "mcpServers": {
    "semavora": {
      "url": "https://mcp.semavora.com/mcp",
      "headers": { "Authorization": "Bearer ${env:SEMAVORA_API_KEY}" }
    }
  }
}

Set SEMAVORA_API_KEY before starting Cursor, using the operating-system steps above, then fully restart it. Environment interpolation keeps the secret out of the configuration. If Cursor reports an authorization error, check that it expands ${env:SEMAVORA_API_KEY} in headers; never paste the key into a project file.

Try it

Ask your agent: “Use Semavora to find the most important problems on my website and help me fix the first one.” It will read your priorities, open the fix task, and after you publish, call verify_fix.