# Use lucid.page from Claude Code

One command connects Claude Code to lucid.page, and from then on your terminal sessions can end with a shareable link instead of a wall of text you copy into Slack like an animal.

Contents

lucid.page turns Markdown into hosted, typeset pages. Claude Code writes plenty of Markdown. You can see where this is going.

# Add the server

claude mcp add --transport http lucid https://lucid.page/mcp

That registers it for the current project. If you want it in every session on your machine, add the user scope:

claude mcp add --transport http --scope user lucid https://lucid.page/mcp

Verify it’s alive by running /mcp inside a session. You should see lucid connected with seven tools.

To publish straight into your account instead of anonymously, put your key on the URL:

claude mcp add --transport http lucid "https://lucid.page/mcp?apiKey=lp_YOUR_KEY_HERE"

# What it’s actually good for

The obvious one: release notes. Finish a feature, then:

Write release notes for what we just did and publish them.

You get a typeset page with a URL, ready for the changelog channel.

The less obvious ones:

Design docs. “Turn this conversation into a design doc and publish it” beats copy-pasting a transcript into Notion and fixing formatting for twenty minutes.
Incident notes. Publish the timeline while it’s fresh, update the same page as you learn more.
Onboarding answers. The next time Claude explains your deploy pipeline to you, have it publish the explanation. New hire asks, you send a link.

Updates work in place when the page is owned, so “update that page from yesterday with the fix we found” keeps the same URL. Every update is a saved revision.

# Worth knowing

Anonymous by default. Without a key, pages are unowned until you open the claim link Claude prints after publishing. Details in Your agent published a page. Now what?
Unlisted by default too. Shareable by link, invisible to search engines. Say “publish it publicly” if you want it indexed.
Keys go in the URL as ?apiKey=lp_... because remote MCP servers don’t get custom headers in most clients. It works the same as an Authorization header.

If you want this in CI instead of interactive sessions, there’s a GitHub Action that publishes on every tag push: Publish release notes from CI.

End