Setup

Connecting the Encelade MCP server takes four steps: create a scoped API token, add the connector, authorize, and verify.

Prefer a screenshot-led walkthrough? See the Connect Claude to Encelade tutorial.

Quick setup

Create an API token

Go to Settings → API tokens → Create Token. The MCP server needs these scopes:

Scope	Used by
`project:read`	`list_projects`, `get_project`
`project:write`	`update_project`
`project:delete`	`delete_project`
`project:plan`	`plan_project`, `generate_project`
`project:generate`	`generate_project`, `get_generation_session` (fallback)
`session:read`	`get_generation_session`

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

Open Settings → Integrations → Add custom connector.
Enter:
- Name: Encelade
- Remote MCP server URL: https://www.encelade.ai/api/mcp
Leave the Advanced settings (manual OAuth fields) empty — Claude Desktop will auto-discover them.
Click Add.

claude mcp add encelade \
  --transport http \
  https://www.encelade.ai/api/mcp

If a browser window doesn't open automatically, run /mcp inside Claude Code, select encelade, then choose authenticate.

codex mcp add encelade \
  --url https://www.encelade.ai/api/mcp

Authorize

A browser window opens at the Encelade authorization page. Paste the API token you created in Step 1 and click Authorize. You'll be redirected back to your client automatically.

Under the hood: the server returns a WWW-Authenticate header on first contact, your client discovers the authorization server, and runs the authorization-code flow with PKCE. Your API token is the credential exchanged for the per-client access token.

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

Claude Desktop: look for Encelade tools in the hammer menu.
Claude Code: run claude mcp list — you should see encelade ✓ connected.
Codex: run codex mcp list.

Then try a simple prompt:

"List my Encelade projects."

If a list_projects tool call returns results, you're set. If you see an authentication error, jump to Troubleshooting.

Rotating or revoking a token

Tokens are managed entirely from Settings → API tokens. Revoking a token immediately invalidates the per-client access token derived from it; the next tool call returns 401 Unauthorized and the client re-runs the authorize flow with the next token you paste.

To rotate without downtime, create the new token first, re-authorize in each client, then revoke the old token.

What's next

Tool reference — parameters, scopes, and example prompts for all seven tools.
Troubleshooting — common errors, rate limits, and support channels.