> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getoasis.org/llms.txt
> Use this file to discover all available pages before exploring further.

# AI client setup

> Connect Oasis manually or through a supported plugin.

Start in [AI connections](https://dashboard.getoasis.org/mcp/connections), available
from the dashboard sidebar and account menu, for setup and connection management.
The [public setup page](https://dashboard.getoasis.org/mcp) needs no sign-in to read.
Production uses `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:

```sh theme={null}
codex mcp add oasis --url 'https://backend.getoasis.org/mcp'
codex mcp login oasis
```

[Client setup help](https://developers.openai.com/codex/mcp)

Oasis plugin listing: **Coming soon**. Use manual setup where supported.

## 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](https://developers.openai.com/plugins/build/plugins)

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](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)

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:

```sh theme={null}
claude mcp add --transport http oasis 'https://backend.getoasis.org/mcp'
```

[Client setup help](https://code.claude.com/docs/en/mcp)

Oasis plugin listing: **Coming soon**. Use manual setup where supported.

## 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:

```text theme={null}
Add a custom remote MCP server named Oasis at https://backend.getoasis.org/mcp. Use OAuth sign-in, use the server’s advertised scopes so I can choose access in the browser, and show me the sign-in link. After I approve, list the Oasis organizations and individually authorized events this connection can access.
```

[Client setup help](https://docs.x.ai/grok-bot/computer-and-apps)

Oasis plugin listing: **Coming soon**. Use manual setup where supported.

## 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](https://cursor.com/docs/context/mcp)

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,
use `oasis: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](https://docs.getoasis.org/features/mcp.md#multiple-organizations).

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](https://www.getoasis.org/contact).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.