MCP access and administration

Use MCP administration for the exact commands and recovery table, hosted setup for client installation, and deployment for the running service. If this skill is loaded remotely without those files, use https://raw.githubusercontent.com/garrytan/gbrain/master/docs/mcp/ADMIN.md. No local brain initialization or personal-agent bootstrap is required to administer an existing server.

Contract

Inspect the user's supplied endpoint and available configuration. A hosting harness may administer its own server only when it has that server's owner credential. A remote administrator needs the same separately supplied authority. An ordinary MCP OAuth token, client secret, admin scope, or full tool surface does not authorize dashboard login or client management.

Use gbrain://capabilities for effective MCP access and administration guidance when available. Its admin URL is orientation, not a login. Without owner authority, provide the exact owner-side command and prerequisite instead of trying successively broader OAuth scopes. Name the server-hosting or authorized administrator harness in the handoff, rather than asking an arbitrary agent.

Owner actions

Commands run against the existing server with gbrain mcp admin … --url URL. Use --admin-token-file PRIVATE_FILE, or the protected GBRAIN_ADMIN_BOOTSTRAP_TOKEN environment variable. Do not print their values. This HTTP path uses the live database connection; do not open a second PGLite process, delete its lock, or start another server to obtain administration.