SecondPage

cc.secondpagePublished by secondpage.ccOfficial publisherv0.2.0Updated Oct 29, 2026

Dashboards, websites, and apps: the Google Drive for everything your AI makes. Edit it together.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

SecondPage is a remote MCP server that acts as a shared home for dashboards, websites and apps built with an AI assistant, with collaborative editing.

What you can do
  • The listing names no individual tools, so capabilities are described only at a high level.
  • Store and organize the dashboards, websites and apps an assistant produces in one place.
  • Work on those artifacts together with other people rather than keeping them local.
  • Connect over a remote HTTP endpoint with OAuth sign-in.
When to use it
Worth considering if you want AI-generated dashboards, sites or small apps kept in a shared, editable space instead of scattered local files, and if several people need to work on them together.
Requirements
A remote MCP endpoint at mcp.secondpage.cc reached over streamable HTTP, plus an OAuth sign-in to a SecondPage account. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the server access to your SecondPage account, and content you publish there is shared with collaborators. The listing gives no tool list, so what the assistant can read, change or delete cannot be verified before connecting.

Installation

In SourceWeft

  1. Open SecondPage in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cc.secondpage%2Fsecondpage/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "secondpage": {
      "type": "http",
      "url": "https://mcp.secondpage.cc/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.