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.

Clients that only support DCR​

A client that stops with an error such as "does not support dynamic client registration" needs a pre-registered client ID. Pre-registered client IDs explains how to ask for one and where common clients take it.

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, or see Call from your own code if you are writing the client yourself.

Building your own client​

Call from your own code explains where your program gets a token. Endpoint and transport describes the requests the server accepts, and Authorization the discovery flow, the metadata document your client has to host, and the checks the server applies to tokens.

Last updated on