AI connections

Connect Festi to your AI assistant

Connect an MCP-compatible assistant to read and manage the Festi events your account can access.

Last updated: October 26, 2026

Connect with OAuth

Claude

Custom connectors are available on Free, Pro, Max, Team and Enterprise. Managed accounts may need an owner to add Festi first. Claude account requirements.

On Claude web, open Customize → Connectors and add a custom web connector at https://planfesti.com/mcp/claude. Choose sign-in authentication and Register automatically if asked, then authorize with Festi.

Official Claude setup guide

ChatGPT

OpenAI lists full custom connections for Business and Enterprise/Edu on the web. Creating one requires the appropriate workspace permissions. ChatGPT account and workspace requirements.

On ChatGPT web, open Plugins → + → Add custom MCP server. Enter https://planfesti.com/mcp/openai, choose OAuth and authorize with Festi. Create and install the plugin, then select it with @ in a chat.

Official ChatGPT setup guide

OAuth grants all available tools within your Festi role, rather than a selection of individual permissions. For narrower access in clients that accept bearer tokens, use personal access tokens. Review changes before approving an assistant action.

The Claude connection supports event planning without AI image generation or image attachment writes. Creating an event through Claude does not generate an automatic cover.

Choose OAuth authentication when your client offers an authentication option.
Sign in to Festi in the browser window that opens.
Review the requested access and approve the connection.

What the connection can access

Announcements posted through a connected assistant appear in the event feed. They do not send push notifications or targeted guest reminders.

OAuth grants all available event tools, not a narrower selection of permissions. Your Festi role still determines what each tool can read or change: guests can manage their own RSVPs and travel, while hosts and authorized co-hosts can manage their events, guests, schedules, documents, and room assignments. Host-only settings remain host-only.

Read tools and write tools are separate. Deletions, replacements, and other potentially destructive changes are marked for the assistant's approval controls. Some actions also require a confirmation argument before the server commits them.

Your assistant must read a guest-list image before sending extracted names to Festi. Review those names and any suggested room assignments before asking it to apply them. Exports return CSV text in batches; ask for every batch. Whether that becomes a downloadable file depends on your assistant.

Connected assistants receive the results of the tools they call. Optional AI, search, and media tools can send the information needed for that operation to the relevant service provider. See the Privacy Policy.

Scoped tokens for scripts

Clients that accept a bearer token can use a Personal Access Token from Access tokens. Choose only the permissions your script needs and an expiration date. The full token is shown once; keep it private and send it in the Authorization header.

Tokens do not support operations that require a signed-in user context, including co-host management, event links, and activity RSVPs. Use OAuth for these operations.

Disconnect or get help

Remove the connection in your assistant to stop using it there. Revoke a Personal Access Token in Access tokens to prevent further requests with that token. Disconnecting an assistant does not delete existing event data or copies of results already received by that assistant.

If authorization fails, reconnect with OAuth at the exact URL above. For help or a request about your data, contact the Festi team.