Cursor MCP: publish a web page

Add the Quicky.Page MCP server to Cursor and its agent can publish any output — release notes, a summary, a generated doc — as a public web page without leaving the editor. One entry in ~/.cursor/mcp.json, a one-time sign-in, and you get a shareable URL back in chat.

Add the server to Cursor

Edit ~/.cursor/mcp.json (global, applies to every project) or .cursor/mcp.json in your project root, and add the Quicky.Page remote server:

{
  "mcpServers": {
    "quickypage": {
      "url": "https://quicky.page/mcp"
    }
  }
}

Open Settings → MCP. Cursor spots the new server, hits it, gets a 401 with the OAuth metadata, registers itself via Dynamic Client Registration, and opens your browser to sign in. Approve on the consent screen and the tools light up — publish_page and the rest are now callable by the agent.

If Cursor doesn't open the browser automatically (a known intermittent issue), copy the authorization URL from the MCP panel logs and paste it into your browser manually.

Ask Cursor's agent to publish

With the server connected, publishing is a one-line instruction in the agent chat:

Publish the release notes you just wrote as a Quicky.Page and paste the URL here.

Cursor calls publish_page and returns the public URL plus a private edit link. Because you signed in, the page saves to your account and the agent can revise it later with update_page using just the page id — no edit key to copy around. The full tool surface is on the MCP server page.

No-account alternative: local stdio

Don't want to sign in? Point Cursor at the local stdio package instead. It runs as a subprocess via npx, needs no OAuth, and returns the edit key directly so pages stay anonymous:

{
  "mcpServers": {
    "quickypage": {
      "command": "npx",
      "args": ["-y", "@quickypage/mcp-server"]
    }
  }
}

Anonymous pages are editable only through the returned editUrl / editKey, so save the edit link if you want to update the page later. See the stdio setup for details.

What to publish from Cursor

• Release notes or a changelog entry the agent just drafted.
• A generated architecture doc or design write-up.
• A README or onboarding page, shared as a link instead of a file.
• Any markdown the agent produces — headings, lists, code blocks, and callouts all render.

Full tool reference: the MCP server. Using Claude instead? Publish Claude output as a URL. Want a raw curl recipe? See publish a web page from the terminal.