# Add lucid.page to Cursor

Cursor speaks MCP, lucid.page has a remote MCP server, and the two get along with about five lines of JSON. No account needed, no local process, nothing to keep running.

Contents

Once connected, the Cursor agent can publish Markdown as typeset pages and paste you the link. Release notes, design docs, that explanation of the auth flow you keep re-explaining in Slack.

# The config

Create or edit .cursor/mcp.json in your project root (or ~/.cursor/mcp.json if you want it everywhere):

{
  "mcpServers": {
    "lucid": {
      "url": "https://lucid.page/mcp"
    }
  }
}

Save the file, then open Cursor’s MCP settings and hit refresh, or just restart Cursor. The lucid server should show up with its tools listed.

If you want every published page to land in your lucid.page account instead of being anonymous, put your API key in the URL:

{
  "mcpServers": {
    "lucid": {
      "url": "https://lucid.page/mcp?apiKey=lp_YOUR_KEY_HERE"
    }
  }
}

Keep in mind the project-level file can end up in git. Either use the global config for the keyed version, or make sure .cursor/mcp.json is in your .gitignore before you commit your key to the whole team’s delight.

# Try it

In the agent chat:

Write up a short README section about our rate limiting and publish it.

The agent calls publish_doc, and you get a URL back. Open it, it’s typeset, done. Cursor will ask for tool approval the first time unless you’ve set it to auto-run, that’s normal.

# Worth knowing

Anonymous pages can’t be edited later. If the agent published without a key, use the claim link it prints to pull the page into your account. The whole ownership model is explained in Your agent published a page. Now what?
The default visibility is unlisted. Anyone with the link can read the page, but search engines are told to stay away. Ask for a public page if you actually want it indexed.
Rate limits are generous for normal use. 10 publishes per minute anonymous, 120 per minute with a key. If you’re hitting those, you’re doing something industrial and should probably look at the API directly.
If the server shows zero tools, check the URL has no trailing slash typo and that you’re on a recent Cursor. Older builds had flaky remote MCP support.

Prefer a full desktop chat app? Same server, different buttons: Add lucid.page to Claude Desktop.

End