Connect, publish, undo.

Connect Claude on your phone

share is a remote MCP server, so there is nothing to install — Claude talks to it over HTTPS. The connector syncs with your Claude account, so doing this on the phone also does it on the desktop app.

https://share-flame-nine.vercel.app/api/mcp

1. Create a share account first, in the phone’s browser. Claude will send you back here to sign in, and it is quicker if the account already exists.
2. Open Claude, tap your profile, then Settings.
3. Tap Connectors, then Add custom connector.
4. Paste the URL above. Name it share so it is obvious in the tool list later.
5. Confirm. Claude opens a share sign-in page; sign in and approve access. You are approving Claude to publish to your account — nothing else.
6. Start a chat and say “list my share sites”. An empty list is the correct answer for a new account. An error means the connector did not finish connecting — remove it and add it again.

Connect ChatGPT

ChatGPT adds custom MCP connectors through developer mode, which is available on Plus, Pro, Business, Enterprise and Edu plans — and only on the web, so do this once at chatgpt.com in a browser. The connector is then available in your conversations.

https://share-flame-nine.vercel.app/api/mcp

1. Create a share account first. ChatGPT will send you here to sign in during setup.
2. On chatgpt.com, open Settings, then Apps & Connectors → Advanced settings, and switch on Developer mode.
3. Back in Connectors, choose Create. Name it share, paste the URL above as the MCP server URL, and pick OAuth for authentication.
4. Confirm. ChatGPT opens a share sign-in page; sign in and approve access. You are approving ChatGPT to publish to your account — nothing else.
5. In a chat, say “list my share sites”. ChatGPT asks before running write tools like publishing — that confirmation prompt is expected, not an error.

Connect Cursor

Cursor speaks MCP natively, so the whole setup is one JSON entry. share supports OAuth with dynamic client registration — no client ID or secret to create.

{
  "mcpServers": {
    "share": {
      "url": "https://share-flame-nine.vercel.app/api/mcp"
    }
  }
}

1. Create a share account first, in your browser.
2. Open Cursor’s Settings, then Tools & MCP, and add a new MCP server — or paste the JSON above into ~/.cursor/mcp.json directly. Put the same block in a project’s .cursor/mcp.json to scope it to that project instead.
3. Cursor opens a browser window to sign in to share. Approve access, and the server shows its tools in the MCP list.
4. In an Agent chat, say “list my share sites”. An empty list is the correct answer for a new account.

Publish your first site

You do not write HTML and you do not upload anything. Describe the page and say publish; the assistant writes the files and calls the tools.

Build a one-page site for my Saturday trail race — start times, a parking note, and a link to the route map. Then publish it with share and send me the URL.

1. The assistant calls prepare_deployment with every file it intends to publish — path, size, content type and SHA-256. The reply shows you that list before a single byte moves.
2. It uploads the bytes to the edge, then calls finalize_deployment. The server checks every stored object against the manifest and only then makes the version live.
3. You get a card back with the live URL and the page itself rendered in it, so you can see what went out without leaving the chat. In a client that does not render cards, the same result carries a QR code — point a phone camera at it.
4. If the page 404s for the first few seconds, that is expected. See below.
5. Want a specific name? Say “publish it as ridgeline-race”. Slugs are lowercase letters, digits and hyphens, 3 to 63 characters.

Changing the page later is the same sentence again: ask for the edit and say publish. Each publish is a new immutable version of the same slug, and the URL does not change.

Roll back a publish

Every version stays exactly where it was written, so going back does not re-upload anything — it moves the pointer the edge reads.

Roll my share site ridgeline-race back to the previous version.

1. The assistant confirms first. rollback_site is marked destructive in the tool definition precisely so it asks.
2. Prefer buttons? Open the dashboard, pick the site, and roll back from its version list. The same audit entry is written either way.
3. Rolling back does not delete the version you left. Publishing again moves forward from the version that is currently live.

When something looks wrong