Connect Gemini CLI

Checked against vendor docs 2026-09-29, not tested end-to-end

The steps below follow Gemini CLI's documentation "MCP servers with the Gemini CLI". We have not yet signed in to NameBeta from Gemini CLI ourselves.

Before you start

• Gemini CLI.
• A NameBeta account, or create one on the sign-in page during setup.
• A pre-registered client ID. Gemini CLI registers itself with an OAuth server only through Dynamic Client Registration, which NameBeta does not offer, and its documentation does not mention Client ID Metadata Documents. Its maintainers closed the request for CIMD support without plans to add it. Ask for a client ID as described under Pre-registered client IDs, naming Gemini CLI and the redirect URI http://localhost:7777/oauth/callback.

Add the server

Gemini CLI reads MCP servers from settings.json:

File	Scope
~/.gemini/settings.json	All your projects
.gemini/settings.json	The current project

Add a namebeta entry under mcpServers, with the client ID you received:

{
    "mcpServers": {
        "namebeta": {
            "httpUrl": "https://namebeta.com/api/mcp",
            "oauth": {
                "enabled": true,
                "clientId": "<client ID>",
                "redirectUri": "http://localhost:7777/oauth/callback"
            }
        }
    }
}

• httpUrl selects the Streamable HTTP transport; url would select SSE.
• redirectUri fixes the port. Without it Gemini CLI picks a random port, which does not match the redirect URI registered for your client ID. If port 7777 is taken on your machine, ask for a different one when you request the client ID.

Sign in

1. Start Gemini CLI and run /mcp auth namebeta. Your browser opens the NameBeta sign-in page.
2. Sign in and approve access, then return to the terminal.

gemini 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 brewlab? Of the taken ones, which are for sale?

Gemini CLI runs check_availability. The answer should mix taken, for-sale and available domains; the tool's example shows the result of 2026-09-29.

Disconnect or switch account

• gemini mcp remove namebeta removes the server from the project configuration; add -s user if you added it to ~/.gemini/settings.json.
• To use a different NameBeta account, see Switch accounts, then run /mcp auth namebeta again.

If it does not connect

Run /mcp list in Gemini CLI to see the server's error, then see Troubleshooting.