MCP Server
Connect Claude, Cursor, and other AI assistants to Encelade through the Model Context Protocol — list, generate, and manage presentations from natural-language prompts.
Encelade exposes a Model Context Protocol (MCP) server so AI assistants can interact with your workspace directly. Once connected, Claude (or any MCP-compatible client) can browse your projects, draft outlines, generate full presentations, and update or delete decks — all from natural-language prompts.
What you can do
- Browse decks — list projects and inspect their pages, theme, and collaborators.
- Plan a presentation — generate an outline you can review before committing to a full generation.
- Generate a presentation — produce a 1–200 page deck from a topic and outline hints; poll for progress.
- Update or delete — rename projects, change themes, or permanently remove decks.
Supported clients
The MCP server speaks standard streamable HTTP and OAuth 2.0, so any MCP-compatible client can connect:
- Claude Desktop (custom connector)
- Claude Code (
claude mcp add) - Codex (
codex mcp add) - Any other client that supports streamable HTTP MCP with OAuth 2.0 discovery
For clients that don't yet speak streamable HTTP, the same endpoint also serves an SSE fallback at /api/mcp/sse (with messages posted to /api/mcp/message). Prefer streamable HTTP when both are supported.
Endpoint
https://www.encelade.ai/api/mcpAuthentication
Every request requires a Bearer token. Clients that support OAuth 2.0 discovery (RFC 9728) — including Claude Desktop, Claude Code, and Codex — pick up the authorization server automatically and walk you through a browser-based authorize step. The token you paste in that step is a scoped API token you create in Settings → API tokens.
See Setup for the step-by-step flow per client.