Quicky.Page

Publish Claude output as a URL

Connect the Quicky.Page remote MCP server to Claude once, then ask Claude to publish any answer as a public web page. You get a shareable URL like quicky.page/abc123 back in the same chat — no copy-paste into a separate editor, no per-page login.

The fastest path: the remote MCP server

Claude (Claude.ai web, Desktop, Mobile, and Claude Code) speaks the Model Context Protocol. Add Quicky.Page's remote MCP server as a custom connector and Claude gains a publish_page tool it can call on its own. Sign in to Quicky.Page once during setup; after that, every page Claude publishes saves to your account automatically.

Claude.ai (web, Desktop, Mobile)

  1. Open Claude.ai → Settings → Connectors → Add custom connector.
  2. Paste the server URL: https://quicky.page/mcp
  3. Click Connect, sign in to Quicky.Page (Google or magic-link email), and approve the connector.
  4. Back in Claude, ask it to publish. The connector is shared across web, Desktop, and mobile — set it up once.

Claude Code (CLI)

Add the server from the terminal:

claude mcp add --transport http quickypage https://quicky.page/mcp

Then run /mcp inside Claude Code, pick quickypage, and complete the browser sign-in.

Ask Claude to publish

Once connected, publishing is a sentence. After any answer you want to keep, say:

Publish your last answer as a Quicky.Page and give me the URL.

Claude calls publish_page, and returns the public URL plus a private edit link. Because you're signed in, the page lands in your account and shows up in the History menu on quicky.page — and Claude can edit it later with update_page without you pasting any key. The full tool set (publish_page, update_page, get_page, upload_image, list_pages, and more) is documented on the MCP server page.

No account? Two alternatives

If you'd rather not sign in, you have two anonymous paths to the same result:

  • Local stdio MCP. The @quickypage/mcp-server npm package runs as a local subprocess for Claude Desktop with no OAuth — pages are anonymous and the edit key is returned to the agent. See the stdio setup.
  • Raw HTTP. Paste the markdown Claude gave you into a single curl call. No connector, no account:
curl -X POST https://quicky.page/api/v1/publish \
  -H 'content-type: application/json' \
  -d '{
    "title": "Notes from Claude",
    "content": "# Summary\n\nPaste the markdown Claude gave you here."
  }'

The response includes a public url and a private editUrl. This is the same endpoint the HTTP API documents in full.

What you can publish from Claude

  • A long explainer or research summary, turned into a clean page.
  • A cleaned-up Claude conversation you want to share with a link.
  • Launch notes, a one-page bio, or a project README.
  • Any markdown answer — headings, lists, callouts, and code blocks all render.

Full tool reference: the MCP server. Working in Cursor instead? Publish a web page from Cursor. Prefer the terminal? See publish a web page from the terminal.