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

# Connect an AI assistant

> Connect an MCP-compatible assistant to Oasis, choose its access, and manage your organization's content from a conversation.

Oasis MCP lets an AI assistant work with your organization's pages, events, members,
artwork, notifications, and analytics. You sign in with your Oasis account and choose
which organizations the connection can access.

MCP is an opt-in beta. It must be enabled for your organization and in the Oasis
environment before you can connect. If it is unavailable, contact your Oasis administrator.

## Before you connect

You need an Oasis account with **organization administrator** access and an AI client
that supports remote MCP servers over **Streamable HTTP** with **OAuth** sign-in.
Being an event administrator or page editor alone does not grant access to this integration.

The assistant can receive content and member information from the organizations you
authorize. Choose an AI client whose data handling is appropriate for your organization.

## Connect to Oasis

1. Open your AI client's settings for MCP servers, connectors, or integrations.

2. Add a remote server named **Oasis** with this URL:

   ```text theme={null}
   https://backend.getoasis.org/mcp
   ```

3. Start the client's connection flow. Sign in on the Oasis dashboard when prompted.

4. Check the client name, requested permissions, and organizations on the consent page.
   Select only the organizations you want this connection to access; none are selected
   automatically.

5. Approve the connection and return to your AI client. Ask it to list the Oasis
   organizations it can access.

Use the server URL above, rather than the URL of this documentation page. You do not
need to copy an Oasis password, Firebase token, or API key into the assistant.

If your organization is testing in staging, use `https://stg.backend.getoasis.org/mcp`
and sign in at `stg.getoasis.org`. Staging and production use separate connections;
check the environment before making changes.

## Choose the right access

| Access requested by the client | What it allows |
| - | - |
| Read only (`oasis:read`) | Read supported content, membership, events, and analytics in selected organizations. |
| Read and manage (`oasis:manage`, with read access) | Create, edit, and remove supported content and memberships; manage permissions; send invitations and notifications. |

The consent screen shows what the client requested. To use read-only access, choose
that scope in a client that supports it before authorizing the connection.

Oasis checks your current administrator access and the organization's MCP setting on
each organization tool call. A connection cannot keep administering an organization
after you lose that access.

## Things you can ask

Start with a read to confirm the organization and content the assistant is working with:

* “List the Oasis organizations this connection can access.”
* “Show the pages in our retreat event.”
* “Summarize the upcoming notifications for this organization.”
* “Show attendance-related groups and the event schedule.”

For changes, make the target and intended outcome explicit:

* “Draft a welcome page for this event. Show me the text and wait for my approval before saving.”
* “Rename this page to ‘Sunday School’ and leave its content unchanged.”
* “Prepare a notification for the volunteers group. Show me its audience, message, and scheduled time before creating it.”

**Writes take effect immediately.** Oasis MCP does not add a separate approval step
to every tool call. Ask your assistant to confirm important changes before calling
a write tool. Creating a notification without scheduling it sends it immediately;
invitations can send email.

## Supported work

The available tools cover organization details and branding; events, memberships,
groups and schedules; pages and navigation tabs; calendars; artwork; tags;
notifications and audience counts; and analytics.

Global user-profile changes, platform-wide administration, organization cloning, and
permanent notification-group deletion are not exposed. Existing invitees' global
profiles are preserved. Notification groups can be archived.

For artwork, the assistant creates an upload URL, uploads an image, and finalizes it.
Finalization accepts PNG, JPEG, or WebP images up to **10 MiB** and **40 million
pixels**. Keep uploads within those limits; oversized or invalid images cannot be
finalized. Upload URLs expire after ten minutes. Artwork references must belong to
the selected organization.

## Retries and uncertain results

Each write requires an `idempotencyKey`, which identifies that specific change. Your
client should reuse the same key and arguments when retrying it. A completed write
returns its saved result instead of executing again.

If a request times out or reports an uncertain result, inspect the affected item in
Oasis before trying again. Do not use a new key to repeat an uncertain invitation or
notification: the original action may already have happened. Ask Oasis support for
help reconciling uncertain delivery.

Tool results include target IDs and dashboard links so you can check the outcome.

## Disconnect an assistant

Open [AI connections](https://dashboard.getoasis.org/mcp/connections) in the dashboard
and choose **Revoke access** for the connection. Future calls using that connection
are rejected. Revocation does not undo changes already made or recall sent messages.

To change which organizations a client can access, revoke the connection and connect
again with the intended selection. Staging connections are managed on the
[staging dashboard](https://stg.getoasis.org/mcp/connections).

## Troubleshooting

| What you see | What to do |
| - | - |
| Endpoint not found, or “AI connections are not enabled” | Confirm the server URL and environment. MCP may not be enabled there yet. |
| Your organization is missing from consent | Confirm you are an organization administrator, the organization is active, and its MCP beta feature is enabled. |
| Sign-in or consent request expired | Restart the connection flow in your AI client. |
| An item cannot be found | Check the selected organization and item ID. References from another organization are rejected. |
| Too many requests | Wait at least a minute, then retry reads. For writes, preserve the original retry key. |
| A connection stops working | Check revocation and your current admin access. If a refresh token was reused, reconnect. |

For help, use [Oasis support](https://www.getoasis.org/contact). Include the environment,
tool name, and the error you received. Do not send passwords, access tokens, or signed
upload URLs.


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