Available transports
| Transport | Entry | Current public status |
|---|---|---|
| Hosted Streamable HTTP | https://slidesfly.com/api/mcp | Live; Bearer API key required |
| stdio | @slidesfly/mcp | Public npm package · v0.1.0 |
Hosted MCP configuration
Configure a Streamable HTTP MCP client with the endpoint and an Authorization header. The exact client configuration shape depends on the Agent host.
{
"url": "https://slidesfly.com/api/mcp",
"headers": {
"Authorization": "Bearer sk_..."
}
}Tool surface
| Tool | Purpose | Hosted input note |
|---|---|---|
publish | Publish a new deck or update an owned deck. | content_base64, filename, optional deck ID |
list | List owned decks. | API-key owner only |
versions | List owned deck versions. | Deck ID |
restore | Copy a previous version into a new live version. | Deck ID and version |
claim | Claim known anonymous decks. | Explicit deck/claim-token items |
status | Report auth and server state. | No local config in hosted mode |
Authentication model
Hosted MCP is stateless and does not expose set_api_key. Create or manage your key in account settings, then send it asAuthorization: Bearer sk_… on every MCP request. The raw secret is shown only once; Slidesfly stores its hash.
| Key scope | Hosted MCP access | REST API access |
|---|---|---|
full | All hosted tools | Owned-deck APIs |
mcp:inspect | status only | None |
Use mcp:inspect for connector directories that only need to verify endpoint health. Use a separately named full key only when an integration must publish or manage decks.
Directory scanners that support the static MCP server-card convention can inspect capability metadata across the authentication wall at /.well-known/mcp/server-card.json.
Slidesfly's official MCP Registry namespace is verified through the public HTTP proof at /.well-known/mcp-registry-auth. The corresponding signing key is never served by the website.
The public stdio package can reuse the CLI's local config and includes set_api_key. Run the verified release with npx -y @slidesfly/mcp@0.1.0.
Registry readiness
The hosted endpoint and this human-readable page provide a stable verification target. Official MCP Registry, Smithery, Glama, and curated-list submission still require a current metadata check and, for source-based listings, a public maintained repository.