Use SecondPage in Claude

SecondPage is a connector for Claude. Once it is connected, Claude can create and manage Pages, the shareable web pages SecondPage publishes, on your behalf, inside a SecondPage organization you choose.

This guide is for the person connecting SecondPage, not for the agent doing the work.

Before you start

You need:

• A SecondPage account. Sign-up is free (the Starter plan has no cost).
• A SecondPage organization. SecondPage work always belongs to an organization, never to a bare personal account. You can create one during setup if you do not already have one.

Add the connector

claude.ai, Claude Desktop, and mobile

Add SecondPage as a connector from Claude's connector settings using this server address:

https://mcp.secondpage.cc/mcp

Claude will start an OAuth sign-in with SecondPage the first time you use the connector, or when you add it. You do not need an API key for this path.

Cowork

Add the same server address in Cowork's connector settings. Cowork follows the same OAuth sign-in described below.

Claude Code

Add the connector from the command line:

claude mcp add --transport http secondpage https://mcp.secondpage.cc/mcp

Claude Code opens the same OAuth sign-in the first time it calls a SecondPage tool.

Sign in and choose an organization

The first time a Claude client uses SecondPage, you sign in (or sign up) with SecondPage, then land on a page at /app/connect to confirm two things:

• Which organization the connector publishes to. If you belong to more than one organization, you choose one from a list. If you belong to exactly one, that organization is already selected. If you belong to none, you are prompted to create one before you can continue.
• The agent name SecondPage uses to label this connector's work, for example on Pages it creates and in the audit log. You can edit this name.

Confirming creates a saved connection between your SecondPage account, that Claude client, and the organization you picked. Claude does not ask you to pick again on later calls unless you deliberately switch, or you lose access to the organization you had chosen (for example, if you are removed from it).

You can return to /app/connect at any time to change which organization new Pages publish to, or to rename the connector's agent identity. Changing organization only affects new Pages; Pages the connector already created stay in the organization they were published to.

What Claude can do

Claude reaches SecondPage through 21 tools. In everyday terms, they fall into two groups.

Read (Claude looks something up)

• See your organization's context, such as its name and available templates.
• Ask for the approval link to switch organizations. Claude cannot switch organizations on its own; it can only hand you the same /app/connect link above for you to approve in a browser.
• List and read your Pages, including their content and structure.
• List the agents connected to your organization.
• Read comments left on a Page, including full comment threads.
• Read who opened a Page and how far they read, so Claude can draft a follow-up without you reading a chart first.
• Look up available data connections and their schema, and preview what a live-data connection would render.
• Export a Page in a supported format.
• Assemble supplied slides into a standard deck bundle without publishing it or calling an AI model.

Write (Claude changes something)

• Create a new Page.
• Update an existing Page's content.
• Add a comment to a Page.
• Upload media (images or video) to attach to a Page.
• Set up a new data connection, or configure how one supplies data to a Page.
• Load the authoring instructions and record that the agent has acknowledged them.

An agent can also move a Page it created to Trash, to take back something it published in error. The Page is unpublished but not destroyed, and you can restore it from Trash.

Claude can change who can see a Page it made for you. Making a Page more private happens right away. Making it more public does not: Claude hands you a link, and the change only happens once you open it and confirm. That is deliberate. Claude reads comments and connected data while it works, and text it reads can be written by anyone, so SecondPage does not let anything Claude read result in your work being published more widely without you saying so.

Trashing a Page Claude did not create, adding or removing specific people, and API-key issuance remain human-only actions in the app.

Confirmation prompts

Whether Claude asks you to confirm an action before running it is controlled by the Claude client you are using (claude.ai, Claude Desktop, Cowork, or Claude Code), not by SecondPage. SecondPage marks which of its tools change data and which ones can publish externally, and Claude clients use that information to decide when to pause for your approval. Review confirmation prompts before publishing or changing where new work appears.

Visibility of what Claude creates

Pages Claude creates follow the same visibility rules as Pages created any other way:

New Pages default to organization visibility. If Claude publishes something you want kept private, or want to share publicly, change its visibility from the Page's sharing controls in SecondPage. See Sharing and visibility.

What data SecondPage receives

When you use the connector, SecondPage receives the tool calls Claude makes on your behalf: the content you ask it to publish or update, the organization and agent identity tied to your connection, and standard request metadata. SecondPage does not receive your Claude conversation itself, only the tool calls and their arguments. Work the connector does is attributed to the agent name you set during sign-in, and is visible to your organization the same way any other agent's activity is, including in the audit log.

Troubleshooting

Claude cannot reach the SecondPage server. Confirm the address is exactly https://mcp.secondpage.cc/mcpCopied with no trailing slash or path changes, and that your network allows outbound HTTPS to it.

Stuck on the organization picker. You need to belong to at least one SecondPage organization to continue. Create one from the link on the connect page, then reopen the connector's connection flow. If you expected to already belong to an organization and do not see it listed, you may have been removed from it; ask an organization owner to re-invite you.

Asked to sign in or approve again unexpectedly. This can happen if your saved connection's organization is no longer valid for you (for example, you left or were removed from it), or if the Claude client issued a new client registration. Sign in and, if prompted, re-pick an organization; this does not create duplicate Pages or lose existing work.

Disconnecting or revoking access. From SecondPage, open Agents in your organization, open the connected agent, and use Disconnect to remove an OAuth connection, or revoke its API keys if it also has any. From Claude, remove the SecondPage connector from your client's connector settings. Either side is enough to stop new activity; doing both fully separates the two.

Support

For help connecting SecondPage to Claude, email support@secondpage.cc.