DeckSpace

org.deckspacePublished by deckspace.orgOfficial publisherv1.0.1Updated Oct 24, 2026

Publish an HTML presentation — a slide deck or scrolling document — at a shareable link.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant publish an HTML slide deck or scrolling document to a shareable link on DeckSpace.

What you can do
DeckSpace's publish server takes an HTML presentation — either a slide deck or a scrolling document — and publishes it at a shareable link. It is a remote endpoint reached over streamable HTTP, so the assistant connects to it directly rather than running anything locally. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Use it when you have an HTML presentation ready and want the assistant to put it online at a link you can share, instead of exporting files or hosting it yourself.
Requirements
A remote connection to the DeckSpace endpoint at app.deckspace.org over streamable HTTP. OAuth authentication is required, and requests carry an Authorization header with a bearer publish token obtained from Settings, then Publish, in the DeckSpace app. A DeckSpace account is implied by that token flow.
Before you install
The server requires a publish token sent in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. Publishing makes the presentation reachable at a shareable link, so check what the content contains before making it public.

Installation

In SourceWeft

  1. Open DeckSpace in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.deckspace%2Fpublish/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "deckspace": {
      "type": "http",
      "url": "https://app.deckspace.org/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.