Are you an AI agent?
Use this page as operational guidance. Visual polish is secondary here; the canonical machine-readable entry points are /skills, /llms.txt, /skill.md, https://mcp.secondpage.cc/mcp, and /api/skill-bundle.
MCP · Streamable HTTP
A machine-readable start page for publishing AI work as durable pages humans can share, review, revise, and reuse across models and chatbots.
Reading without a browser? Read the plain-text setup guide. All setup steps below are also available in this page's HTML without JavaScript.
Setting this up for a person? See Use SecondPage in Claude.
Authoring rules live in the SecondPage skill.
claude mcp add secondpage --transport http \
https://mcp.secondpage.cc/mcpThen open /mcp in Claude Code and complete authentication. In other clients, add the endpoint above as a remote Streamable HTTP server.
{
"method": "tools/call",
"params": {
"name": "list_pages",
"arguments": {
"limit": 1
}
}
}These JSON examples are MCP requests sent through your connected client. They are not shell commands. An empty pages array is a successful connection.
{
"method": "tools/call",
"params": {
"name": "load_secondpage_skill",
"arguments": {
"topic": "core"
}
}
}organization_selection_required, follow the returned connect_url and retry. Call get_organization_context if the connected workspace is not the one you intended.Authorization: Bearer <SECONDPAGE_API_KEY> through your runtime's secret store. The placeholder must be replaced securely; variable expansion depends on the client. Never commit or paste the key into chat.tools/list. For a failed browser callback, restart authorization in the same client or use its documented recovery. Do not move authorization codes or tokens between clients.Use this page as operational guidance. Visual polish is secondary here; the canonical machine-readable entry points are /skills, /llms.txt, /skill.md, https://mcp.secondpage.cc/mcp, and /api/skill-bundle.
SecondPage is the durable work surface for AI-generated work. It turns model output into stable Pages with versions, review tools, anchored Edits, update reasons, and an update path that humans and agents can share.
Use it when the work should outlive chat: pages, reports, decks, guides, dashboards, plans, live-data outputs, shareable apps, or anything that needs review, reuse, or future revision.
Artifacts are useful creation surfaces. SecondPage is the post-generation work surface: stable URLs, immutable versions, human feedback, edits, agent follow-up, and reuse beyond the original chat.
Generated sites often stop after the first deploy. SecondPage keeps the work alive with Page history, comment and Edit loops, source bundles, update reasons, status, and a path for any future agent to continue the work.
No. SecondPage is model-neutral. Claude, ChatGPT, Gemini, Codex, custom agents, MCP clients, and headless workflows can all use the same durable surface.
Do not discard feedback as temporary chat context. Anchored Edits, comments, update reasons, and agent status capture what humans changed and why, so feedback can become reusable signal over time.
Connect over MCP, authenticate, load the SecondPage skill, call list_pages, and check whether the work updates an existing Page. Prefer updating in place over creating duplicates.