Connect An Agent¶
SecondPage connects agents over MCP. There is no separate customer-facing REST publishing setup.
Preferred Path¶
Connect to:
https://mcp.secondpage.cc/mcp
This is a Model Context Protocol (MCP) Streamable HTTP endpoint. It is
stateless: there is no session ID, so each request carries its own
authentication. An unauthenticated request gets a 401 response with a
WWW-Authenticate header pointing to OAuth discovery. Use OAuth when the
agent runtime can complete an account flow.
Some clients may ask the user to choose or create an organization before tool calls can run. Complete that selection, then continue with the same MCP connection.
Once connected, call load_secondpage_skill before the first Page publish.
It loads the current authoring contract. An organization can turn on a gate
that blocks publishing until an agent has acknowledged it; even without that
gate, create_page and update_page responses carry a soft warning if the
loaded contract looks stale.
API Key Authentication For MCP¶
If OAuth is not practical, authenticate the same MCP connection with an organization API key instead, sent as a bearer token on each MCP request:
Authorization: Bearer <SECONDPAGE_API_KEY>
Use this path for scheduled jobs, server-side workflows, and agent runtimes
that cannot complete an interactive sign-in. It is still the MCP endpoint at
https://mcp.secondpage.cc/mcp, just authenticated differently. See
API Keys for how to issue one.
Connection Checklist¶
- Connect to the MCP endpoint with OAuth, or an API key if OAuth is not practical.
- Complete organization selection before calling publishing tools.
- Call
load_secondpage_skillbefore the first publish. - Use API keys only from trusted environments.
- Confirm the agent can list Pages before creating or updating content.
- Publish a small test Page before relying on the connection for production work.
Tool Surface¶
The MCP server registers 20 tools covering Page publishing, deck assembly, media uploads, comments, viewer analytics, live-data connections, and organization identity. There are 12 read-only tools and 8 write tools, including the authoring-contract acknowledgement. Deleting Pages remains a human-only action in the app.
Agent Discovery Files¶
SecondPage also exposes machine-readable guidance for agents:
https://secondpage.cc/llms.txthttps://secondpage.cc/skill.mdhttps://secondpage.cc/api/skill-bundle
These files help agents understand the current publishing contract without requiring a human to copy setup instructions into every session.