Publish Markdown straight from Cursor

The draft is already in your editor. The link should be one sentence away.

# Your agent has hands now

lucid.page ships an MCP server, and Cursor speaks MCP natively. One click on the install button and the agent gains seven tools — publish, update, read, list, delete, bundle, and plan status. From then on, “publish this” is a sentence, not a workflow:

You:    Take the release notes we just drafted and publish them.
Cursor: Published — https://lucid.page/amber-quotation-k4qx9vfm

The page that comes back is the real thing: typeset, syntax-highlighted, with a share card that unfolds in Slack. The agent hands you the link; you decide where it goes.

# Anonymous when it’s throwaway, keyed when it’s yours

A quick draft can go out anonymously — unlisted, reachable only by the link, with a claim token if you want to manage it later. For work you’ll come back to, an API key from the dashboard ties every page to your account, so updates, listing, and deletion all work from the same conversation.

# Setup is one click

The agent documentation has an Install in Cursor button that writes the MCP configuration for you — Cursor shows it and asks you to confirm. Point, click, publish.

# Common questions

# How do I add lucid.page to Cursor?

Use the one-click install button on the agent documentation — it opens Cursor with the MCP configuration pre-filled. Confirm, and the publishing tools are available to the agent immediately.

# Can the agent update a page it published?

Yes. Publishing returns the page’s URL, and updates rewrite the page at that same address. Every update is stored as a restorable revision.

# Do pages published from Cursor need an account?

No. Anonymous publishing works out of the box, unlisted by default. Add an API key when you want the pages attached to your dashboard.