MCP - Better Auth — ContextQMD

Better Auth hosts a remote MCP server that exposes documentation search, examples, and setup help to any MCP-capable client (Cursor, Claude Code, Open Code, and others).

Endpoint: https://mcp.better-auth.com/mcp

This is separate from the MCP plugin, which adds MCP provider authentication to your app. The server above is for consuming Better Auth docs inside your editor or agent.

Using the CLI

Run the Better Auth CLI and pick your client:

bash

npx auth@latest mcp

With no flags, the command lists supported targets. You can pass a target directly:

<Tabs items={["Cursor", "Claude Code", "Open Code", "Manual"]}> <Tab value="Cursor"> bash title="terminal" npx auth@latest mcp --cursor

This opens Cursor with a deeplink so the server is added to your MCP configuration.

You can also use the one-click control on this site:

<AddToCursor />

</Tab> <Tab value="Claude Code"> ```bash title="terminal" npx auth@latest mcp --claude-code ```

This runs `claude mcp add` with the Better Auth URL. If that fails, the CLI prints the exact command to run yourself.

</Tab> <Tab value="Open Code"> ```bash title="terminal" npx auth@latest mcp --open-code ```

This merges a `better-auth` entry into `opencode.json` in the current directory (remote transport, URL above).

</Tab> <Tab value="Manual"> ```bash title="terminal" npx auth@latest mcp --manual ```

Writes or merges `mcp.json` in the current working directory with:

```json
{
  "better-auth": {
    "url": "https://mcp.better-auth.com/mcp"
  }
}
```

For **Cursor**, you can add the same `better-auth` entry to MCP config—commonly `~/.cursor/mcp.json` (user) or `.cursor/mcp.json` (project)—using the shape your Cursor version expects for HTTP servers (`url` for remote MCP).

Restart or reload MCP in your client after changes.

</Tab> </Tabs>