Skip to content

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

Point MCP token docs at the restored MCP Access page

Claude4e6b9b7bfe96
diff --git a/docs/cli/mcp-connect.mdx b/docs/cli/mcp-connect.mdx
index 6611a5e9..61948c5a 100644
--- a/docs/cli/mcp-connect.mdx
+++ b/docs/cli/mcp-connect.mdx
@@ -137,7 +137,7 @@ then registers itself, opens a browser, and you approve access on beacon.sh. No
by Beacon, and access is revoked from the dashboard.
**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), export it, and connect
+with `beacon mcp token create` (or at [beacon.sh → Dashboard → 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. It needs the `mcp:token:create` permission, which
+revoked at [beacon.sh → Dashboard → 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:
+[beacon.sh → Dashboard → 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 8034336e..8fb5a202 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 and held in an environment
+`beacon mcp token create` or at [beacon.sh → Dashboard → 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.
diff --git a/docs/cloud/lenses/lenses-mcp.mdx b/docs/cloud/lenses/lenses-mcp.mdx
index fe61b992..3bbad055 100644
--- a/docs/cloud/lenses/lenses-mcp.mdx
+++ b/docs/cloud/lenses/lenses-mcp.mdx
@@ -18,8 +18,9 @@ release one, and choose who can find it. Deleting a lens is only possible in the
pasted into a tool call.
<Note>
- Access tokens created with `beacon mcp token create` are always read-only. Use browser sign-in
- to publish lenses.
+ Access tokens created with `beacon mcp token create` are always read-only. To publish with a
+ token instead of browser sign-in, create one with **Read + publish lenses** access on the
+ [MCP Access](https://beacon.sh/dashboard/mcp) page.
</Note>
## Lens tools
diff --git a/docs/deployment/managed-mcp.mdx b/docs/deployment/managed-mcp.mdx
index fd5fc98c..34cd30dc 100644
--- a/docs/deployment/managed-mcp.mdx
+++ b/docs/deployment/managed-mcp.mdx
@@ -159,11 +159,29 @@ beacon mcp connect --token-env BEACON_MCP_TOKEN
Beacon writes only the variable's name into the harness configuration, never the token.
-- Tokens from `beacon mcp token create` are **read-only**. Use OAuth to publish lenses.
+- Tokens from `beacon mcp token create` are **read-only**. To publish lenses with a token, create
+ one with **Read + publish lenses** access on the [MCP Access](https://beacon.sh/dashboard/mcp)
+ page instead.
- Tokens start with `bcn_mcp_`, are shown once, and expire after 90 days by default
(`--expires-in-days`, up to 366, or `0` for never).
- You can have up to 25 active tokens.
+## Manage access in the dashboard
+
+The **MCP Access** page at [beacon.sh/dashboard/mcp](https://beacon.sh/dashboard/mcp), under
+**Identity** in the dashboard sidebar, shows everything that can reach your history over MCP:
+
+- **What Beacon MCP can access:** the server URL, and what read and write access allow.
+- **Connected apps:** every client you approved in the browser, whether it can publish lenses, and
+ when it was last used. Select **Disconnect** to remove one.
+- **Access tokens:** every token, its access, expiry and last use. Create a token here, including
+ one that can publish lenses, or select **Revoke**. A token is shown once, when you create it.
+- **Agents on your devices:** each supported agent Beacon found on your connected devices, and
+ whether `beacon-managed` is already configured in it. For one that is not, the page gives you the
+ `beacon mcp connect --harness <name>` command to run on that device.
+
+Disconnecting an app or revoking a token takes effect within 30 seconds.
+
## Security
- **Session content is data, not instructions.** Your history can contain text that looks like