Setup
Connect the approved Encelade app in ChatGPT or set up Claude, authorize your workspace, and verify the connection. Includes Claude Code and Codex setup.
Connect Encelade to ChatGPT or Claude to browse your presentations and generate decks from a conversation. Encelade is now an approved ChatGPT app: install it from the directory, then connect your Encelade account. This tutorial also covers manual MCP setup for Claude, Claude Code, and Codex.
Both clients use OAuth: you sign in and approve access in your browser. You do not need to create an API key, install a package, or edit a configuration file.
Before you start
- Sign in to your Encelade account. You need an admin or editor role in the workspace you want to connect.
- For ChatGPT, use an account and workspace where the Encelade app is available. Your workspace administrator may need to enable it.
- For Claude, use the web or desktop app. Custom connectors are available on Free, Pro, Max, Team, and Enterprise; Free allows one custom connector. On Team or Enterprise, ask an organization owner to add it first. Enterprise members with Manage access to Libraries permission can also add connectors.
For Claude and other manually configured MCP clients, use these connection details. ChatGPT's approved app already includes the server configuration.
| Field | Value |
|---|---|
| Name | Encelade |
| Server URL | https://www.encelade.ai/api/mcp |
| Authentication | OAuth |
| OAuth client registration | Automatic / dynamic client registration (DCR) |
| Manual client ID and secret | Leave empty |
Copy the full server URL, including www and /api/mcp.
If your menus differ, use the official ChatGPT instructions or Claude instructions.
Connect your assistant
Connect Encelade
- Open the ChatGPT directory from Plugins and search for Encelade.
- Open the Encelade app and select Install (or the + button).
- Select Connect if prompted, then sign in to Encelade and complete the workspace authorization step below. If sign-in is not requested during installation, connect when you first use the app.
- Start a new chat, type @, and select Encelade to use it in that conversation.
The approved app handles the MCP configuration for you. No developer mode, custom plugin, server URL, or manual OAuth credentials are required.
Authorize
A browser window opens on Encelade:
- Sign in to the Encelade account that has access to your presentations.
- Check the client name and redirect host match the assistant you are connecting.
- Select the workspace you want the assistant to use. If you have one eligible workspace, it is already selected.
- Review the requested access, then select Authorize. The browser returns you to your assistant.
The connection can read and edit decks and generate new ones within the selected workspace, subject to your permissions and plan limits. It expires after 90 days and can be revoked in Encelade settings. To connect the other assistant, repeat setup and authorize it separately.
For manually configured MCP clients, the server answers the first request with 401 and a WWW-Authenticate header. Your client discovers the authorization server, registers itself at /api/oauth/register, sends you to /oauth/authorize, then exchanges the returned code at /api/oauth/token with PKCE (S256). The access token is bound to the workspace you picked, covers every tool, and expires after 90 days.
Discovery endpoints (useful if you're debugging the OAuth dance manually):
| Purpose | Path |
|---|---|
| Protected-resource (RFC 9728) | /.well-known/oauth-protected-resource |
| Authorization-server (RFC 8414) | /.well-known/oauth-authorization-server |
| Authorization endpoint | /oauth/authorize |
| Token endpoint | /api/oauth/token |
| Dynamic client registration | /api/oauth/register |
Verify
- ChatGPT: start a chat and select Encelade using @.
- Claude: enable Encelade under + → Connectors in the chat.
- Claude Code: run
claude mcp list— you should seeencelade ✓ connected. - Codex: run
codex mcp list.
Then try a simple prompt:
Use Encelade to list my presentation projects. Do not create or change anything.
Look for a successful list_projects tool call and your workspace's presentations. An empty list is also a successful connection if the workspace has no projects. A general explanation of Encelade without a tool call does not verify the connection.
Once that works, try:
Use Encelade to create a five-slide presentation about renewable energy for investors. Cover the market, key technologies, opportunities, risks, and next steps. Check its progress and give me the presentation link when it is ready.
Review any action approval your assistant displays. Generation uses your Encelade credits and plan limits; the assistant should check progress before returning the completed deck link.
If setup does not work
| Problem | What to do |
|---|---|
| Encelade is missing from ChatGPT or installation is disabled | Search for Encelade in the directory and check that you are in the intended ChatGPT account and workspace. Ask your workspace administrator to enable the app if needed. See the OpenAI plugin guide for current menus. |
| Claude has no “Add custom connector” option | On Team or Enterprise, ask an organization owner to add Encelade. On Free, check whether your single custom connector slot is already in use. |
| The client asks for a client ID or secret | Select automatic / dynamic client registration. In Claude, choose Register automatically. Do not enter an Encelade API token into an OAuth credential field. |
| The sign-in page did not open | Open the installed plugin or connector and select Connect. Allow the browser to open the sign-in window, then finish authorization. |
| No workspace is available to authorize | Complete Encelade signup, or ask a workspace admin to give your account an editor or admin role. |
| Encelade is connected but the assistant does not use it | Select Encelade with @ in ChatGPT or enable it under + → Connectors in Claude. Start a new chat and retry the read-only prompt above. |
| Projects are missing or the workspace is wrong | Confirm which Encelade account and workspace you authorized. Reconnect and select the intended workspace. |
| Authentication expired or was revoked | Reconnect from your assistant and repeat the Encelade authorization step. |
For tool errors and generation limits, see MCP troubleshooting.
Connect with an API token
Clients that can't run the OAuth flow, and scripts or CI jobs without a browser, can send a personal API token as an Authorization: Bearer header instead.
Create an API token
Go to Settings → API tokens → Create Token. Workspace admins see this tab, as do members who have been allowed to create personal tokens; if you don't, ask a workspace admin to create a token for you. The MCP server needs these scopes:
| Scope | Used by |
|---|---|
project:read | list_projects, get_project |
project:write | update_project |
project:ai-chat | edit_project |
project:delete | delete_project |
project:generate | generate_project, get_generation_run, cancel_generation_run |
session:read | get_generation_run without generation access |
session:write | cancel_generation_run without generation access |
theme:read | list_themes |
theme:write | create_theme, update_theme, delete_theme |
Grant only the scopes you need. A read-only token is fine if you only want browsing.
Copy the token immediately — it is only displayed once.
Add the connector with the token
Export the token as ENCELADE_API_TOKEN, then:
claude mcp add encelade \
--transport http \
https://www.encelade.ai/api/mcp \
--header "Authorization: Bearer $ENCELADE_API_TOKEN"Revoking access
Each authorized client shows up in Settings → API tokens as OAuth via client name; a workspace admin can revoke it there. A revoked or expired token fails the next tool call with 401 Unauthorized; re-run the authorize step from the client to reconnect (see Troubleshooting).
Each account can hold five active OAuth connections at a time; revoke one before authorizing another client.
To rotate an API token without downtime, create the new token first, update the client's header, then revoke the old token.
What's next
- Tool reference — parameters, scopes, and example prompts.
- Troubleshooting — common errors, rate limits, and support channels.