Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Name the MCP Access page by its sidebar location in the MCP CLI docs

Claude6c0bf5a8baa0
diff --git a/docs/cli/mcp-connect.mdx b/docs/cli/mcp-connect.mdx
index 61948c5a..143fb276 100644
--- a/docs/cli/mcp-connect.mdx
+++ b/docs/cli/mcp-connect.mdx
@@ -134,10 +134,10 @@ a comment in the config, because some harnesses rewrite their config files and d
**OAuth is the default and the recommended mode.** Connect writes only the URL. The first time the
harness connects, Beacon Cloud answers `401` with a pointer to its OAuth metadata. The harness
then registers itself, opens a browser, and you approve access on beacon.sh. No secret is written
-by Beacon, and access is revoked from the dashboard.
+by Beacon, and you can disconnect the app on the [MCP Access](https://beacon.sh/dashboard/mcp) page.
**A personal token** is for harnesses or setups where browser sign-in does not work. Create one
-with `beacon mcp token create` (or at [beacon.sh → Dashboard → MCP Access](https://beacon.sh/dashboard/mcp)), export it, and connect
+with `beacon mcp token create` (or at [Dashboard → Identity → MCP Access](https://beacon.sh/dashboard/mcp)), export it, and connect
with `--token-env`:
```bash
@@ -173,7 +173,7 @@ JSON on stdout instead. Beacon never writes the token to a file.
| `--json` | Print the token and its details as JSON |
The token reads your Beacon Cloud data, counts toward the limit of 25 active tokens, and is
-revoked at [beacon.sh → Dashboard → MCP Access](https://beacon.sh/dashboard/mcp). It needs the `mcp:token:create` permission, which
+revoked at [Dashboard → Identity → MCP Access](https://beacon.sh/dashboard/mcp). It needs the `mcp:token:create` permission, which
`beacon login` requests and the sign-in page lists; a session from an older `beacon login` is
refused with a prompt to sign in again.
@@ -209,7 +209,7 @@ Connect writes these entries (OAuth mode shown, then what `--token-env NAME` add
These harnesses have no MCP OAuth support Beacon has confirmed, so connect writes nothing for them.
It prints the command or snippet instead, with a `<token>` placeholder for a token from
-[beacon.sh → Dashboard → MCP Access](https://beacon.sh/dashboard/mcp):
+[Dashboard → Identity → MCP Access](https://beacon.sh/dashboard/mcp):
- GitHub Copilot CLI: `copilot mcp add --transport http beacon-managed <url> --header "Authorization: Bearer <token>"`
- Cline: a `streamableHttp` entry in `cline_mcp_settings.json`
diff --git a/docs/cli/mcp.mdx b/docs/cli/mcp.mdx
index 8fb5a202..2d2afb40 100644
--- a/docs/cli/mcp.mdx
+++ b/docs/cli/mcp.mdx
@@ -32,7 +32,7 @@ the other:
`beacon mcp connect` registers `beacon-managed` in Claude Code, Codex CLI, Cursor, VS Code,
Gemini CLI, OpenCode and Oh My Pi. By default it writes only the URL, and each harness signs in with OAuth.
With `--token-env`, the config instead references a personal token, created with
-`beacon mcp token create` or at [beacon.sh → Dashboard → MCP Access](https://beacon.sh/dashboard/mcp) and held in an environment
+`beacon mcp token create` or at [Dashboard → Identity → MCP Access](https://beacon.sh/dashboard/mcp) and held in an environment
variable. For other harnesses it prints the steps to add the
server by hand.