open-brain-web-gateway
Hosts the OAuth consent and sign-in UI for the gateway, along with privacy and terms pages.
OAuth-protected remote MCP gateway for Perplexity web client, forwarding approved calls to an existing Open Brain operational memory without direct access to the long-lived access key.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@open-brain-web-gatewaywhat do I have stored about project Phoenix?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Open Brain web gateway
OAuth-protected remote MCP gateway for Tony's Gemini Spark and Perplexity web clients. It forwards approved calls to the existing vanilla Open Brain and never creates another brain.
Boundaries
Open Brain is operational memory, not Continuity, COTA, Current-State Tracker, or owner-acceptance authority.
No automatic chat capture. Capture tools are for explicit requests only.
The vanilla Open Brain repository and Edge Function remain unchanged.
Browser clients receive short-lived OAuth tokens, never the long-lived Open Brain access key.
OAuth tokens are validated and then terminated at this gateway; they are not passed to the upstream Open Brain.
Related MCP server: Brainbase MCP
Components
open-brain-web-gateway: OAuth-protected Streamable HTTP MCP relay with client/user allowlists, exact and summary aliases, authoritative post-write receipts, and a server-enforced/readonlyroute that exposes only the seven bounded read tools.docs/: GitHub Pages email-link sign-in and OAuth consent UI, plus privacy and terms pages.open-brain-oauth-ui: deployable source retained as a fallback for a future custom Supabase domain; the default Supabase Functions domain intentionally rewrites HTML to plain text.
Required live configuration
Supabase OAuth 2.1 Server enabled with authorization path
/oauth/consent.Auth Site URL:
https://derivedbetter.github.io/open-brain-oauth-ui.Authorization path:
/oauth/consent/and redirect allowlist includeshttps://derivedbetter.github.io/open-brain-oauth-ui/**.Pre-registered confidential clients for Gemini full access, Gemini Spark read-only access, Perplexity, and Claude.
Edge secrets:
OPEN_BRAIN_ALLOWED_EMAILS=<approved-email>OPEN_BRAIN_OAUTH_CLIENT_IDS=<full-gemini-client-id>,<perplexity-client-id>,<claude-client-id>OPEN_BRAIN_READ_ONLY_OAUTH_CLIENT_IDS=<read-only-gemini-client-id>optional
OPEN_BRAIN_OAUTH_AUDIENCES=authenticated,<gateway-url>existing
MCP_ACCESS_KEYremains server-side.
Dynamic client registration stays disabled for the pilot.
Validation
npm test
npx -y supabase@latest functions deploy open-brain-oauth-ui --project-ref zoptbgumxukgpkgbtnpz --no-verify-jwt
npx -y supabase@latest functions deploy open-brain-web-gateway --project-ref zoptbgumxukgpkgbtnpz --no-verify-jwtTest discovery and unauthenticated failure before connecting a client:
GET /functions/v1/open-brain-web-gateway/.well-known/oauth-protected-resourcereturns protected-resource metadata.GET /functions/v1/open-brain-web-gateway/readonly/.well-known/oauth-protected-resourcereturns distinct read-only protected-resource metadata.unauthenticated
POST /functions/v1/open-brain-web-gatewayreturns401and an OAuthWWW-Authenticatechallenge.authenticated
tools/liston/functions/v1/open-brain-web-gateway/readonlyomits every write/delete tool, and direct write calls fail closed.OAuth clients are endpoint-scoped: read-only client tokens are rejected by the full-access route, and full-access client tokens are rejected by the read-only route.
invalid user, client, issuer, audience, and expired tokens fail closed without an upstream call.
Rollback
Revoke the affected OAuth client, disable the connector in Gemini or Perplexity, disable Supabase OAuth Server if no clients remain, and delete only the two gateway Edge Functions. Existing Open Brain data and the ChatGPT, Codex, and agy integrations remain unchanged.
This server cannot be deployed
Maintenance
Related MCP Connectors
OAuth 2.1 short-link tools for AI agents with scoped tokens, approvals, audit logs, and revocation.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
OAuth Multi-LLM Orchestrator
- OpenOakOAuthorg.openoak
Secure AI access to OpenOak tasks, notes, and Kanban boards.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI clients like Claude to interact with Cartena tools via MCP, supporting remote OAuth or local stdio authentication.-
- AlicenseNot gradedqualityBmaintenanceEnables management of Brainbase agents, components, evals, tasks, and more via a remote MCP connection with OAuth authentication.2MIT
- AlicenseNot gradedqualityDmaintenanceOAuth token broker for AI agents to securely act on a user's behalf across third-party APIs (Gmail, Slack, GitHub, Notion, etc.) by vaulting tokens server-side and never exposing them to the LLM.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible assistants to securely access external systems like Slack through permission-scoped, idempotent tools with tenant isolation, delegated OAuth consent, and an immutable audit trail.MIT