Connect Claude Code

:::info Last verified 2026-09-28

Verified with Claude Code 2.1.283: the server connected over OAuth and all five tools returned results.

:::

Add the server

claude mcp add --transport http namebeta https://namebeta.com/api/mcp

namebeta is the local name Claude Code shows for the server; pick any name you like. By default the server is added for the current project only, on your machine. Use --scope to change that:

Scope	Where it is saved	Who gets it
local (default)	Your user settings, keyed to the current project	You, in this project
user	Your user settings	You, in every project
project	.mcp.json in the project root, meant to be committed	Everyone who opens the project

For example, to have NameBeta in every project:

claude mcp add --transport http --scope user namebeta https://namebeta.com/api/mcp

The configuration holds only the URL. Tokens are stored by Claude Code on each machine, so a committed .mcp.json never contains credentials — each teammate signs in with their own NameBeta account.

Sign in

1. Start Claude Code and run /mcp.
2. Select namebeta and choose Authenticate. Your browser opens the NameBeta sign-in page.
3. Sign in and approve access. The browser tells you when you can return to the terminal.

claude mcp list should now show the server as connected:

namebeta: https://namebeta.com/api/mcp (HTTP) - ✔ Connected

Try it

> Which TLDs are still free for kettlory?

Claude Code asks for permission the first time it calls each tool, then runs check_availability.

Remove or re-authenticate

• claude mcp remove namebeta removes the server (add -s user or -s project if you used that scope).
• To sign in as a different NameBeta account, open /mcp, select namebeta and clear the authentication, then authenticate again.

See Troubleshooting if authentication fails.