Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
List, share, upload, and manage Slideless HTML presentations from any MCP host.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.slideless.ai/mcpRun this in your terminal
claude mcp add --transport http slideless https://mcp.slideless.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"slideless": {
"url": "https://mcp.slideless.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"slideless": {
"type": "http",
"url": "https://mcp.slideless.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.slideless.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain slideless.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 + mcp-handler) at `https://mcp.slideless.ai/mcp`. Listed on the official MCP registry as `ai.slideless/mcp`.
Stateless 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.| Tool | What it does |
|---|---|
slideless_whoami | Identity check — returns org, key name, scopes |
slideless_list_presentations | List owned + invited presentations |
slideless_get_presentation | Full info for one presentation (tokens, collaborators) |
slideless_list_versions | Version history of a presentation |
slideless_get_version | Manifest of a specific version |
slideless_download_version | Manifest + inline text-file contents (HTML/CSS/JS up to 256 KB each) |
slideless_upload_html_presentation | Upload a single-file HTML deck |
slideless_upload_presentation_files | Upload a multi-file deck (base64 array) |
slideless_add_share_token | Mint a public viewer URL |
slideless_set_token_version_mode | Pin or unpin a token to a version |
slideless_unshare_presentation | Revoke one or all share tokens |
slideless_share_via_email | Send the share URL by email |
slideless_invite_collaborator | Grant another user dev access (sends email) |
slideless_uninvite_collaborator | Revoke a collaborator |
slideless_list_collaborators | List collaborators on a presentation |
slideless_delete_presentation | Permanently delete a presentation |
slideless_search_marketplace | Search the public marketplace for remixable presentations, apps, and plans (no key) |
slideless_get_marketplace_listing | Full detail for one marketplace listing by slug (no key) |
slideless_remix_listing | Remix a listing — returns the manifest plus inline contents of every text file (no key) |
slideless_publish_listing | Publish a pushed presentation to the marketplace (requires marketplace:publish scope) |
slideless_star_listing | Star a marketplace listing on behalf of the connected user |
slideless_unstar_listing | Remove the connected user's star from a listing |
pnpm install
pnpm dev # next dev → http://localhost:8787
Test with the MCP Inspector:
npx @modelcontextprotocol/inspector
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_ " \ -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)