https://backend.getoasis.org/mcp;
staging uses https://stg.backend.getoasis.org/mcp and a separate sign-in.
MCP must be enabled for the environment and each organization. A client needs remote
Streamable HTTP and OAuth support. Workspace policy or plan restrictions may apply.
Codex
Run the commands below, then complete Oasis sign-in in your browser. Choose read-only or read and write access on the Oasis authorization page. Codex desktop and IDE clients on the same host share the configuration. If Oasis is already configured, check its URL before signing in again. Local setup does not automatically enable cloud access; use the ChatGPT option for cloud and web plugin setup. Codex commands:ChatGPT
In ChatGPT Plugins, choose the plus button, then Add custom MCP server. Enter the Oasis server URL, use OAuth sign-in, and choose Create as a plugin. Install and connect it in the cloud workspace where you will use it. Your plan and workspace policy control availability; ask your workspace administrator if custom plugins are unavailable. Choose read-only or read and write access on the Oasis authorization page. Clients configured to request only read access will show only that option. Client setup help Oasis plugin listing: Coming soon. Use manual setup where supported.Claude
In Customize → Connectors, add a custom web connector named Oasis and paste the server URL. Use OAuth and automatic client registration; leave client secrets and request headers empty. Connect, finish Oasis sign-in, and enable Oasis for your conversation. Your workspace owner may need to allow custom connectors first. Choose read-only or read and write access on the Oasis authorization page. Clients configured to request only read access will show only that option. Client setup help Oasis plugin listing: Coming soon. Use manual setup where supported.Claude Code
Run the command below, then use /mcp inside Claude Code to select Oasis and authenticate. Choose read-only or read and write access on the Oasis authorization page. Claude Code command:Grok Bot
Ask your Bot to add Oasis as a custom remote MCP server. Follow its Connect or Authenticate card and finish Oasis sign-in in your browser. Check the requested permissions before approving. Grok Bot connections are shared across your Bots and remain subject to your team’s connector policy. Choose read-only or read and write access on the Oasis authorization page. Clients configured to request only read access will show only that option. Grok Bot setup prompt:Cursor
Add a remote MCP server in Cursor’s MCP settings with the server URL and complete OAuth sign-in. If configuring JSON, use an mcpServers entry with the url field. Choose read-only or read and write access on the Oasis authorization page. Clients configured to request only read access will show only that option. Client setup help Oasis plugin listing: Coming soon. Use manual setup where supported.Other clients
Add the remote URL using the client’s MCP configuration and complete OAuth sign-in. Do not paste passwords, Firebase tokens, or access tokens into chat or configuration. Review the requested permissions before approving. For clients with scope configuration, useoasis:read for read-only access, or oasis:read oasis:manage to allow changes.
Select organizations or individual events on the Oasis consent page. Event admins can
authorize their events when the parent organization has MCP enabled. Use
list_authorized_events for event-only grants. Ask the assistant to list
its authorized organizations and confirm the name and ID before working. Names may
repeat. See multiple organizations and retries.
A plugin listing does not mean every account or environment can connect. If the server
returns 404, MCP may not be enabled yet. Use Oasis support.