Connect Cursor

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

The mcp.json format below follows Cursor's MCP documentation; we have not yet signed in to NameBeta from Cursor ourselves. The file format is stable; the settings screen changes more often, so look for the MCP section of Cursor Settings if a label below no longer matches.

Before you start

• Cursor.
• A NameBeta account, or create one on the sign-in page during setup.
• A pre-registered client ID. Cursor signs in to an MCP server through Dynamic Client Registration, which NameBeta does not offer, or with static client credentials; its documentation does not list Client ID Metadata Documents, and Cursor staff said on the feature request on 2026-05-13 that there is no timeline for them. Ask for a client ID as described under Pre-registered client IDs, naming Cursor and its redirect URIs http://localhost:8787/callback (desktop app) and https://www.cursor.com/agents/mcp/oauth/callback (web and Cursor Agents).

Add the server

Cursor reads MCP servers from mcp.json. Use the file in your home directory to have NameBeta in every project, or the one in a project to share it through the repository:

File	Scope
~/.cursor/mcp.json	All your projects
.cursor/mcp.json	The current project

Add a namebeta entry with the URL and, in the auth block, the client ID you received:

{
    "mcpServers": {
        "namebeta": {
            "url": "https://namebeta.com/api/mcp",
            "auth": {
                "CLIENT_ID": "<client ID>",
                "scopes": ["profile", "email"]
            }
        }
    }
}

If the file already lists other servers, add namebeta next to them inside mcpServers.

• Keep scopes as shown. Without it, Cursor takes the scopes from the authorization server's metadata, which lists scopes NameBeta does not grant to MCP clients.
• Do not add CLIENT_SECRET. The client ID is for a public client and has no secret.
• Do not add headers with a token. Cursor gets its own token through OAuth, and a hard-coded token expires.

Sign in

1. Open Cursor Settings and go to the MCP section (Tools & MCP). The namebeta server is listed and marked as needing authentication.
2. Click its sign-in button. Your browser opens the NameBeta sign-in page.
3. Sign in and approve access, then return to Cursor. The server should then show as connected and list five tools.

Try it

In Agent chat, ask:

Look up the MX records of github.com.

Cursor runs lookup_dns and should answer with github-com.mail.protection.outlook.com, the record dig MX github.com returns too.

Disconnect or switch account

• To stop using NameBeta, remove the namebeta entry from mcp.json.
• To use a different NameBeta account, see Switch accounts.

If it does not connect

See Troubleshooting if sign-in does not complete.