Pagelive MCP connector

Publish the pages you build with AI — straight from the conversation — as private, branded, view‑tracked links.

Pagelive turns any HTML page (a proposal, deck, report, or demo) into a clean link you can actually send. Publish it from Claude, get a link that's private by default (noindex, optional password, served from an isolated content plane on Cloudflare), then see who opened it — opens, unique viewers, dwell time, by day, country, referrer — bot‑filtered, with an email the moment it's opened. Pages can carry a reply form whose submissions come back into the conversation. Update anytime; the link never changes.

This is the Claude plugin + connector manifest + docs for Pagelive's hosted MCP server. The server is hosted by Pagelive (you don't run or install anything); this repo is the public home for the Claude plugin manifest, server.json, the tool reference, and example usage. Sign in with your Pagelive account — a free account works.

• Website: https://pagelive.io/mcp

• Docs / quickstart: https://pagelive.io/docs/quickstart-mcp

• Connector URL (remote, OAuth): https://app.pagelive.io/api/mcp

Connect

Claude plugin

The Claude plugin is defined in .claude-plugin/plugin.json. It declares the hosted HTTP MCP endpoint directly and includes the skill in skills/, which Claude discovers automatically. For a local Claude Code checkout, load it with:

claude --plugin-dir /path/to/pagelive-mcp

Authenticate the pagelive MCP server with /mcp when prompted. You do not need to add the same MCP server manually when using the plugin.

Connect without the plugin

The server is remote and uses OAuth 2.0 — there's nothing to install. Add the URL to any MCP‑capable client and sign in with your Pagelive account.

Claude (web / desktop) — Settings → Connectors → Add custom connector → paste https://app.pagelive.io/api/mcp → sign in when prompted.

Claude Code

claude mcp add --transport http pagelive https://app.pagelive.io/api/mcp

Any client that reads server.json — point it at this repo's server.json, or find Pagelive in the MCP Registry under io.pagelive/pagelive.

Related MCP server: drop

Tools (7)

Example prompts

1. "Publish this page with Pagelive and give me the link."

2. "Update my Q3 proposal page with this new version — keep the same link."

3. "How many people opened my deck this week, and how long did they read?"

4. "Did anyone reply to the proposal form? Show me the responses."

5. "List my published pages and tell me which got views yesterday."

Live demos

• https://pagelive.site/p/vantage-series-a-deck

• https://pagelive.site/p/q2-performance-report

• https://pagelive.site/p/q3-growth-proposal

Skill

This repo includes an optional Agent Skill that teaches the publish → share → track workflow, so an agent reaches for Pagelive at the right moment.

Auth & privacy

The plugin starts no local process and installs no packages. It has no hooks or LSP servers. MCP requests go to https://app.pagelive.io/api/mcp: publishing and editing send your HTML and selected page settings to Pagelive; reads retrieve the pages, analytics, form replies, and review data authorized for your account. Sign-in uses Pagelive OAuth; no credentials are bundled in this repository. HTML pages can load external assets you include in them. The hosted service's privacy policy applies.

OAuth 2.0 sign‑in (free account works); no API key juggling. Published pages are noindex by default and can be password‑gated; analytics are bot‑filtered and contain no PII.

License

MIT — applies to the contents of this repo (manifest, docs, examples, skill). The hosted Pagelive service and its server source are separate and proprietary.

Validate a release

Run both checks from the repository root before pushing a new version:

claude plugin validate --strict .claude-plugin/plugin.json
claude plugin validate --profile directory --strict .

Increment the version in .claude-plugin/plugin.json for each plugin release. server.json is the separate MCP Registry manifest; it is not a Claude plugin manifest. Submit the repository root as the plugin folder. The developer portal performs additional checks and must scan the new commit before the directory listing can proceed.