Skip to main content

Connect VS Code

NameBeta's tools work in VS Code's chat in agent mode.

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

The steps below follow VS Code's documentation "Add and manage MCP servers in VS Code", its MCP developer guide for the install link, and the VS Code 1.106 release notes, which added sign-in through Client ID Metadata Documents. We have not yet signed in to NameBeta from VS Code ourselves. If a command name below no longer matches, search the Command Palette for MCP.

Before you start​

  • VS Code 1.106 or later, with chat enabled.
  • A NameBeta account, or create one on the sign-in page during setup.

Add the server​

With one click​

Install NameBeta in VS Code

The link opens VS Code, which shows the server and asks you to confirm the installation. It adds the same entry as the file below.

In mcp.json​

VS Code reads MCP servers from mcp.json:

FileScope
The file that the MCP: Open User Configuration command opensAll your workspaces
.vscode/mcp.jsonThe current workspace

Add a namebeta entry under servers:

{
    "servers": {
        "namebeta": {
            "type": "http",
            "url": "https://namebeta.com/api/mcp"
        }
    }
}

The MCP: Add Server command in the Command Palette does the same through a guided flow: choose the HTTP server type, enter the URL, name the server namebeta, and pick Global or Workspace.

Do not add a headers entry with a token or an oauth block. VS Code identifies itself with a Client ID Metadata Document, so it needs no client ID.

Sign in​

  1. Start the server: VS Code offers to start it when you open chat, or run MCP: List Servers, select namebeta and choose Start Server. Confirm that you trust the server when VS Code asks.
  2. VS Code asks you to sign in. Allow it; your browser opens the NameBeta sign-in page.
  3. Sign in and approve access, then return to VS Code.

MCP: List Servers shows the server as running, and the tools picker in chat lists its five tools.

Try it​

Open chat, switch to Agent mode, and ask:

Which TLDs are still free for brewlab? Of the taken ones, which are for sale?

VS Code 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​

  • To stop using NameBeta, run MCP: List Servers, select namebeta and uninstall it, or remove the entry from mcp.json.
  • To sign out, open the Accounts menu in the lower left and sign out of NameBeta. To use a different NameBeta account, see Switch accounts.

If it does not connect​

Run MCP: List Servers, select namebeta and choose Show Output to see the server log, then see Troubleshooting.

Last updated on