Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.slideless.ai/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.slideless-mcp https://mcp.slideless.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.slideless-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.slideless.ai/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
MCP server for Slideless. Wraps the Slideless HTTP API as Model Context Protocol tools so users can list, share, upload, and manage HTML presentations from any MCP host (Claude Desktop, claude.ai, ChatGPT desktop, Cursor, etc.) without installing the slideless CLI.
Hosted on Vercel (Next.js App Router + ) at . Listed on the official MCP registry as .
List, share, upload, and manage Slideless HTML presentations from any MCP host.
mcp-handlerhttps://mcp.slideless.ai/mcpai.slideless/mcpStateless Next.js route handler — streamable-HTTP transport, no session store. A per-request McpServer is built on each /mcp call and the user's Authorization header is forwarded verbatim to the Slideless Cloud Functions in europe-west1. No database, no secrets to rotate — the user's token never leaves the request.
Claude / ChatGPT → mcp.slideless.ai/mcp (Vercel / Next.js)
│
▼
europe-west1-slideless-ai.cloudfunctions.net
The server is an OAuth 2.1 resource server. It does not host the auth flow itself — it advertises app.slideless.ai as the authorization server and forwards tokens to the Cloud Functions, which validate them. Two header styles are accepted, both forwarded verbatim:
/mcp returns 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource (RFC 9728), which points at app.slideless.ai. The user signs in / signs up and consents in-browser; no key is ever pasted. New API keys are minted invisibly by the authorization server.Authorization: Bearer cko_… directly.https://mcp.slideless.ai/mcp.cko_… key at https://app.slideless.ai → Settings → API Keys, and set it as the Authorization header.pnpm install
pnpm dev # next dev → http://localhost:8787
Test with the MCP Inspector:
npx @modelcontextprotocol/inspector
# Transport: Streamable HTTP
# URL: http://localhost:8787/mcp
# Header: Authorization: Bearer cko_<your-key>
Or with raw curl (initialize handshake):
curl -s http://localhost:8787/mcp -X POST \
-H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer cko_<your-key>" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}'
Type checking: pnpm typecheck.
Pushed to main → Vercel auto-deploys production (project codika/slideless-mcp). Manual deploy:
vercel deploy --prod --scope codika
Rate limiting is enforced at the edge by Vercel WAF rules (managed via the vercel firewall CLI), matching path starts-with /mcp:
mcp-per-ip → 60 req / 10s, keyed by IPmcp-per-key → 600 req / 60s, keyed by the Authorization header (so each API key / OAuth token gets its own bucket)Both return 429 when exceeded, before the function runs. Recreate with:
vercel firewall rules add "mcp-per-ip" --condition '{"type":"path","op":"pre","value":"/mcp"}' \
--action rate_limit --rate-limit-window 10 --rate-limit-requests 60 --rate-limit-keys ip --yes
vercel firewall rules add "mcp-per-key" --condition '{"type":"path","op":"pre","value":"/mcp"}' \
--action rate_limit --rate-limit-window 60 --rate-limit-requests 600 --rate-limit-keys header:authorization --yes
vercel firewall publish --yes
app/
├── layout.tsx # minimal root layout
├── page.tsx # landing page (/)
├── [transport]/route.ts # MCP endpoint (/mcp); per-request client + 401 challenge
└── .well-known/oauth-protected-resource/route.ts # RFC 9728 metadata → app.slideless.ai
src/
├── config.ts # base URL, server identity (SEP-973 branding), instructions
├── http.ts # OAuth metadata, CORS, 401 challenge builders
├── server.ts # registerAllTools entry point
├── slidelessClient.ts # typed fetch wrapper around the Cloud Functions
├── types.ts # wire shapes (mirrors slideless-app types/)
├── errors.ts # SlidelessApiError + wrapToolErrors
└── tools/
├── identity.ts # slideless_whoami
├── presentations.ts # list / get / versions / download / delete
├── upload.ts # upload_html / upload_files (3-step orchestration)
├── sharing.ts # tokens, version mode, unshare, email
├── collaborators.ts # invite / uninvite / list
└── marketplace.ts # search / get / remix / publish / star / unstar
server.json # MCP registry metadata (ai.slideless/mcp)
slideless-app — backend Cloud Functions this server proxies (also hosts the OAuth 2.1 authorization server)slideless-cli — npm CLI that uses the same APIslideless-plugin — Claude Code plugin (companion authoring + upload skills)© 2026 MCP Directory.
List, share, upload, and manage Slideless HTML presentations from any MCP host.
{ "mcpServers": { "ai.slideless-mcp": { "url": "https://mcp.slideless.ai/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Slideless is reached over HTTP.
Last checked 2026-11-07. List, share, upload, and manage Slideless HTML presentations from any MCP host.