# Self-hosted remote access and editor integration

Remote dashboard access and the inbound editor MCP surface have different boundaries. Do not assume a setting that enables one enables the other.

## Reach the dashboard
Use the documented private-network or TLS tunnel path for your own gateway. Confirm the destination and authentication before opening it from another device. Avoid exposing a raw unauthenticated port.

The self-hosted account controls can offer password sign-in and two-factor authentication. Devices manages paired clients; revoke a device you no longer trust. Hosted customers use their account’s normal sign-in instead of these operator controls.

## Give an editor read-only context
The documented inbound MCP surface is off by default and is limited to same-machine access. Its six tools are status, memory recall, knowledge search, session search, task listing, and task detail. It does not provide write tools.

Create a dedicated credential with `gideon inbound token create mcp`, enable the external-access master switch and MCP switch, then restart as the [editor guide](https://github.com/Sidiora-Labs/centra-gideon-agent/blob/main/docs/guides/USE_FROM_YOUR_IDE.md) describes. Put the token in your editor’s secure configuration; it is not the dashboard token.

## Respect the actual limit
The source guide documents remote MCP requests being refused before the remote-allow setting takes effect. Do not publish `/mcp` or treat `allow_remote` as a working bypass. A rapid client can also encounter rate limits and need to reconnect.

## External-agent context files
For project-local tools, Legibility can generate reviewed context blocks in supported agent instruction files. That is a separate capability from exposing the MCP server.