# Connect a client (/en/docs/api-mcp/mcp/connect)





The server is configured with a single URL and no credential. Signing in happens in your browser through OAuth, so there is no key to paste, store, or rotate.

```text
https://mcp.centralcsp.com
```

**Settings > AI tools** in the dashboard generates the same snippets with your environment filled in, and is the place to check whether your plan includes the feature.

<img alt="The AI tools page with the Claude Code tab selected, the generated claude mcp add command already carrying the server URL, and the three numbered steps below it" src="__img0" width="1234" height="450" />

## Claude Code [#claude-code]

```bash
claude mcp add --transport http --client-id mcp centralcsp https://mcp.centralcsp.com --scope user
```

Then:

1. Run `/mcp` inside Claude Code and pick **Authenticate**.
2. Sign in with your CentralCSP account in the browser that opens.
3. Run `/mcp` again to confirm the server is connected.

`--scope user` registers it for every project. Leave it out to add it to the current project only, which writes to that project's `.mcp.json`.

## Claude Desktop [#claude-desktop]

Remote servers are added as custom connectors rather than from a config file.

1. Open **Settings**, then **Connectors**, then **Add custom connector**.
2. Paste `https://mcp.centralcsp.com`.
3. Open the advanced settings and enter `mcp` as the OAuth client ID. Leave the client secret empty.
4. Save, choose **Connect**, and sign in.

## Codex CLI [#codex-cli]

```toml title="~/.codex/config.toml"
[mcp_servers.centralcsp]
url = "https://mcp.centralcsp.com"
auth = "oauth"
```

Then:

1. Run `codex mcp login centralcsp` to start the sign-in.
2. Sign in with your CentralCSP account in the browser that opens.
3. Run `codex mcp list` to confirm.

Codex registers itself with the sign-in server, so there is no client ID to set.

Use `.codex/config.toml` inside a trusted project to scope it to that project instead.

## Any other client [#any-other-client]

Most clients take this shape:

```json title="mcp.json"
{
  "mcpServers": {
    "centralcsp": {
      "type": "http",
      "url": "https://mcp.centralcsp.com"
    }
  }
}
```

Restart the client so it picks up the server, then approve the sign-in prompt.

Two variations to expect. Some clients name the transport `streamable-http` rather than `http`, and a few use `servers` as the top-level key. If the client asks for an OAuth client ID, use `mcp` with no secret.

## Next steps [#next-steps]

* [Quickstart](/en/docs/api-mcp/mcp/quickstart)
* [Permissions and safety](/en/docs/api-mcp/mcp/permissions)