Slideless

What the Slideless MCP server does

The Slideless MCP server connects MCP hosts to the Slideless HTTP API for managing HTML presentations. It supports both single-file HTML decks and multi-file decks, plus presentation metadata, version history, sharing links, collaborators, and deletion.

The server also exposes Slideless's public marketplace. Agents can search listings, retrieve listing details, remix a listing, and star or unstar listings. Publishing a presentation to the marketplace is available when the connected credential has the marketplace:publish scope.

How it works

The hosted endpoint is https://mcp.slideless.ai/mcp. It uses the streamable-HTTP transport and runs as a stateless Next.js route on Vercel. A new MCP server instance is created for each request; there is no session store or database in this service.

Authorization headers are passed through to Slideless Cloud Functions in europe-west1, where the credentials are validated. OAuth 2.1 hosts can discover the Slideless authorization server and complete sign-in in a browser. Hosts that support custom headers can send an API key directly as Authorization: Bearer cko_….

The Slideless MCP server accepts OAuth tokens and static API keys through the same authorization header. Requests are subject to edge rate limits: 60 requests per 10 seconds per IP and 600 requests per 60 seconds per authorization key or token. Exceeding either limit returns HTTP 429 before the function runs.

Setup and configuration

For a hosted connection, add https://mcp.slideless.ai/mcp as a custom MCP connector in an OAuth-capable host. The host should discover the authorization flow, open Slideless sign-in, and request consent. No API key needs to be pasted when the host supports this flow.

For a host that requires a static header, create a cko_… API key in Slideless under Settings and API Keys, then configure the host to send it as an Authorization bearer token. The README specifically identifies Cursor and Claude Code as examples of hosts that can use custom headers.

Local development requires Node project dependencies installed with pnpm install, followed by pnpm dev. The local MCP endpoint is http://localhost:8787/mcp. It can be tested with the MCP Inspector using Streamable HTTP or with an HTTP client that sends the authorization header and MCP initialization request.

Tools and capabilities

Presentation tools can identify the current organization, list owned and invited decks, retrieve presentation details, inspect versions, download manifests and inline HTML, CSS, or JavaScript text files, upload decks, and permanently delete presentations. Inline text-file retrieval is limited to files up to 256 KB each.

Sharing tools create public viewer URLs, pin or unpin a share token to a version, revoke one or all tokens, and email a share URL. Collaboration tools invite users with development access, list collaborators, and revoke invitations.

Marketplace tools require no key for public search, listing details, and remix operations. Publishing requires the marketplace:publish scope; starring and unstarring act on behalf of the connected user.

Limitations and notes

The service does not host the Slideless login flow; it advertises app.slideless.ai as the authorization server and relies on the downstream Cloud Functions to validate credentials. Hosts without OAuth support must handle API-key configuration themselves.

The server wraps the Slideless API rather than storing presentation data locally. Uploading multi-file presentations uses a base64 file array, while downloading returns inline contents only for supported text files within the stated size limit. Rate limits are enforced at the hosted endpoint, and credentials must have the scopes needed for restricted operations such as marketplace publishing.