Global MCP connection

Connect Site Bench once. Use it in every project.

Site Bench audits public website URLs, so it does not need repository access or project-specific settings. Add it to your personal MCP configuration and use the same account from every workspace.

Choose your MCP client Create free account

Global installation

Install Site Bench in your MCP client

Choose the client you use. These options install Site Bench at user scope so the connection follows you across projects.

Claude Code

Adds Site Bench to your user scope, making it available in every Claude Code project. Open /mcp after installing if the browser authorization does not start automatically.

Global install command

claude mcp add --scope user --transport http sitebench https://sitebench.ai/mcp

OpenAI Codex

Adds Site Bench to the user-level Codex configuration shared by the Codex CLI, desktop app, and IDE extension. Select Authenticate or run codex mcp login sitebench when prompted.

Global install command

codex mcp add sitebench --url https://sitebench.ai/mcp

Cursor

Open Cursor's MCP installer, review the Site Bench remote URL, and approve the user-level connection. Cursor opens the Site Bench login flow when it first connects.

Install in Cursor

Visual Studio Code

Adds Site Bench to your VS Code user profile, where it is available across workspaces and can sync with your profile settings.

Global install command

code --add-mcp '{"name":"sitebench","type":"http","url":"https://sitebench.ai/mcp"}'

OpenCode

Writes the remote Site Bench server to your global OpenCode configuration. Run opencode mcp auth sitebench if you want to start browser authorization immediately.

Global install command

opencode mcp add sitebench --url https://sitebench.ai/mcp

Windsurf / Cascade

Add this entry to ~/.codeium/windsurf/mcp_config.json, the user-level MCP configuration used across Cascade workspaces.

Global mcp_config.json entry

{
  "mcpServers": {
    "sitebench": {
      "serverUrl": "https://sitebench.ai/mcp"
    }
  }
}

Other MCP clients

Use the remote URL

If your client supports remote MCP with browser authorization, add the Site Bench URL directly.

Remote MCP URL

https://sitebench.ai/mcp

If your client accepts only a local command, use this compatibility bridge instead.

Local command bridge

npx -y [email protected] https://sitebench.ai/mcp

Nothing is added to your repository

Site Bench receives only the tool arguments you explicitly send, such as a public URL or audit ID. It does not read your source tree, environment files, Git history, or local project settings.

Your OAuth credential is stored by your MCP client and sent only to Site Bench over HTTPS. It is never placed in a project configuration or committed to GitHub.

Review or revoke connected apps

MCP setup questions

Should Site Bench be installed globally or per project?

Use global or user scope. Site Bench audits public URLs and does not require repository-specific configuration. Project scope is only useful if a team wants to commit the public endpoint for discovery.

Does Site Bench receive my repository or local files?

No. Site Bench receives only explicit MCP tool arguments. Your coding client may use the returned findings while working locally, but the Site Bench server does not automatically receive source code or project files.

Where is authentication stored?

Your MCP client stores the OAuth authorization in its private credential storage. Each teammate connects their own Site Bench account, and access can be revoked from Connected Apps.