Publish from your AI

Publish straight from the chat you're already in

Works directly with ChatGPT, Claude and Claude Code — so the assistant that wrote your deck can publish it into your workspace and hand you back a link, without a download and an upload in between. Connect it once, then just ask.

Connecting takes a free account — the approval page lets you sign up with Google or an email in a few seconds, then returns you to Allow.

← Back to DeckSpace

Then just ask

Once it's connected, ask the assistant in plain language — “publish this to DeckSpace” — and the deck appears in your sidebar with a share link, ready to send.

It can also work on the decks already there. Ask it to list your decks, read one back, or edit one in place — “fix the Q3 number on my launch deck” — and it changes the HTML behind the same link, saving a version first so any edit can be undone. Decks you built with Create with AI are read-only this way; edit those in the app.

Setup instructions

Hand this to an agent like Claude Code and it wires up the connection itself, then prompts you to approve it once in your browser. No token, no API key, nothing to copy.

DeckSpace MCP server: https://app.deckspace.org/mcp — full instructions: https://deckspace.org/llms.txt

In a chat app — Claude, ChatGPT, Gemini, Grok — you paste https://app.deckspace.org/mcp into its custom-connector settings yourself (in ChatGPT, turn on Developer mode under Settings → Security and login, then add it with the plus button on the Plugins page), then click Allow. Any client that adds a remote (Streamable HTTP) MCP server works. Revoke a connected assistant under Settings → Publish → Connected AIs.

Publishing from a script instead? POST https://app.deckspace.org/api/decks with your publish token (Settings → Publish) in an x-opendeck-token header and a JSON body with title and html returns a live share link.

Also in DeckSpace

Style from Your Template — upload the deck your team already uses (HTML, PowerPoint, PDF or an image) and new AI builds reuse its palette, fonts and layouts.
Redesign that keeps your words — ask for a new look and only the design changes; the words stay as they are.
Slides or Web page — a deck is 16:9 slides or one web page (one scroll or tabs), and Restyle switches a built deck from one to the other.
Update data — upload a new CSV or XLSX and every chart recomputes at the same link; the old data stays in History.

Common questions

How do I publish a deck straight from Claude or ChatGPT?

Add the DeckSpace MCP server once (above) by pasting the endpoint URL and clicking Allow in the browser, then ask the assistant to publish. The deck lands in your workspace and it hands back a link — no download and upload in between.

Can my AI edit a deck that's already on DeckSpace?

Yes — ask it to list your decks, then read or edit one. For a deck it uploaded or published, it edits the HTML in place by find-and-replace and keeps the same share link, saving a version before every change. Decks you composed with Create with AI are read-only over MCP; edit those in the app.

Do I need a token or API key to connect?

No. Paste the endpoint URL and approve once in your browser — that's OAuth, and there's no token to copy. A client that can't run the browser approval can fall back to a per-user publish token from Settings → Publish, in a header or in the URL; in the URL form the token is the credential, so treat it like a password and rotate it from the same screen.

Does publishing from ChatGPT work on every plan?

ChatGPT's developer mode is beta, and on personal Plus/Pro plans write actions like publishing may be restricted to Business/Enterprise/Edu accounts. If ChatGPT refuses to publish, that is a plan limit, not a broken setup.