MCP Clients
Slidev MCP works with any client that supports the Model Context Protocol. No API keys or authentication required — just point your client at the server URL.
Quickest Setup
Most clients just need this URL:
https://mcp.slidev-mcp.org/mcpSelf-hosting? Replace with your own server domain.
Supported Clients
| Client | Type | Guide |
|---|---|---|
| Claude Code | CLI | One command setup |
| Claude Desktop | Desktop app | Custom connector (UI) |
| Cursor | IDE | One-click or JSON config |
| Windsurf | IDE | JSON config |
| VS Code (Copilot) | IDE | JSON config |
| JetBrains IDEs | IDE | UI or JSON config |
| Zed | IDE | JSON config |
| Opencode | CLI | JSON config |
| Gemini CLI | CLI | JSON config |
| ChatGPT | Web / Desktop | Custom connector (developer mode) |
Other Clients
For any MCP client not listed above, use the streamable HTTP transport with your server URL:
https://mcp.slidev-mcp.org/mcpConsult your client's MCP documentation for how to add a streamable HTTP server.
About Transports
Slidev MCP serves Streamable HTTP at /mcp. This is the remote transport defined by the current MCP specification (revision 2026-07-28), which only defines stdio and Streamable HTTP. The older HTTP+SSE transport is deprecated and there is no /sse endpoint, so if your client asks you to choose, pick HTTP / Streamable HTTP, not SSE. Clients that try Streamable HTTP first and fall back to SSE (Claude Code, VS Code) will work without changes.
Configuration key names differ per client (url, serverUrl, httpUrl, type: "remote"), so use the exact format from your client's guide.