Publish pages from Claude

Claude writes well. lucid.page makes sure the result reads well, too.

# From chat scrollback to a real page

A long answer in a chat window is a terrible artifact: it scrolls away, it screenshots badly, and it cannot be linked. With lucid.page connected, Claude can publish the document it just wrote — the design doc, the meeting notes, the postmortem — and hand back a link that opens as a calm, typeset page.

You:    Turn this conversation into a postmortem and publish it.
Claude: Done — https://lucid.page/quiet-incident-7wz2mkht

# Works where Claude works

The MCP server speaks the standard protocol, so it slots into Claude Code on the command line and Claude Desktop alike — Claude Desktop takes it as a connector, Claude Code as a single server entry. The agent documentation has the exact setup for each client.

# The page keeps its source

Every published page exposes its Markdown at /raw/, so whatever Claude publishes stays machine-readable — another agent, a script, or future-you can pick it up as text, not as a screenshot of text.

# Common questions

# Does this work with Claude Code?

Yes. Add the lucid.page MCP server to Claude Code — one command, shown in the agent documentation — and the publishing tools appear in the session.

# And with Claude Desktop?

Same server, same tools. Claude Desktop takes remote MCP servers through its Connectors UI; the documentation walks through it.

# Can Claude publish anonymously?

Yes. Anonymous pages are unlisted by default and come with a claim token. Add an API key when you want pages attached to your account instead.