Status: Experimental. MCP can invoke research actions in the desktop process. Treat client configuration as a permission boundary and verify the current build's controls before enabling a transport.
Safe defaults
- Prefer local stdio.
- Keep remote access disabled unless it is required.
- Keep read-only mode enabled where the build exposes it.
- Review tool approval prompts and activity logs.
- Do not publish a session token or local data path.
The current desktop source defaults the HTTP host to 127.0.0.1, disables remote binding, requires a token, and enables read-only mode. TLS is required for non-loopback binding. Stdio is a separate local process channel and does not use the HTTP token check. Effective values can differ by build and saved settings; verify them before use.
Remote HTTP or SSE access depends on host, token, origin, TLS, and read/write settings in the current build. These controls and their effective values remain configuration-dependent; this page is not a certification of a deployed MCP endpoint.
MCP does not expose internal Supabase, billing, admin, service-role, or security-operation endpoints as a public API. Those are implementation details of the web and desktop products.