Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Publish pages straight from Claude as private, branded, tracked links.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://app.pagelive.io/api/mcp在终端中运行这条命令
claude mcp add --transport http pagelive https://app.pagelive.io/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"pagelive": {
"url": "https://app.pagelive.io/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"pagelive": {
"type": "http",
"url": "https://app.pagelive.io/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://app.pagelive.io/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 pagelive.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.2.1)于41天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, HotCodePush
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
https://app.pagelive.io/api/mcpThe 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.
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.
| Tool | What it does |
|---|---|
publish_page | Publish an HTML page and get a live, shareable, view‑tracked URL. Pass an existing slug to replace a page instead of duplicating it. |
update_page | Edit a page you've published — targeted text edits or a full‑HTML replace. The link never changes. |
list_pages | List the pages you can access (personal + team) with their URLs, workspace, and view counts. |
get_page_stats | View analytics for a page — opens, unique viewers, dwell, top countries. |
list_form_submissions | Read the replies submitted through a page's reply form. |
list_domains | List your connected custom domains (Pro/Team). |
list_workspaces | List the workspaces you belong to (personal + teams). |
This repo includes an optional Agent Skill that teaches the publish → share → track workflow, so an agent reaches for Pagelive at the right moment.
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.
MIT — applies to the contents of this repo (manifest, docs, examples, skill). The hosted Pagelive service and its server source are separate and proprietary.
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.