Skip to main content

Connect other clients

Any MCP client works with NameBeta if it supports:

  • the Streamable HTTP transport, and
  • OAuth 2.1 authorization with Client ID Metadata Documents (CIMD), or a pre-registered client ID.

Point the client at https://namebeta.com/api/mcp, leave any client ID, secret or token fields empty, and sign in when it asks.

Codex​

:::info Last verified 2026-09-28

Commands checked against Codex CLI 0.158.0. The authorization request Codex sends was verified against NameBeta's authorization server on 2026-09-20.

:::

Add the server, then sign in:

codex mcp add namebeta --url https://namebeta.com/api/mcp
codex mcp login namebeta

codex mcp login opens your browser at the NameBeta sign-in page. On a machine without a browser, add --no-browser: Codex prints the authorization URL, and you paste back the URL you land on after approving.

codex mcp list shows the server and whether you are signed in.

Clients that only support DCR​

NameBeta does not offer Dynamic Client Registration (DCR). A client that can only register itself through DCR stops with an error such as "does not support dynamic client registration".

If the client lets you enter an OAuth client ID, we can pre-register it: write to contact@namebeta.com with the client's name and the redirect URIs it uses, and we reply with a client ID. For example, Claude Code takes one with --client-id, and Cursor takes one in the auth block of mcp.json.

Clients that only take a static token​

Some clients can only send a fixed Authorization header. NameBeta has no API keys, and the access tokens it issues are short-lived, so such a client cannot stay connected. Use a client with OAuth support instead.

Building your own client​

Authorization describes the discovery flow, the metadata document your client has to host, and the checks the server applies to tokens.

Last updated on