own.page

page.ownPublished by own.pageOfficial publisherv1.0.0Updated Nov 1, 2026

Build and edit your own.page link-in-bio page: links become widgets, themes, subpages, stats.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant build and edit an own.page link-in-bio page, turning links into widgets, themes, subpages and stats.

What you can do
  • Build and edit an own.page link-in-bio page.
  • Turn links into widgets and arrange page content.
  • Apply and change themes.
  • Manage subpages.
  • Review page stats.
When to use it
Useful when you maintain an own.page link-in-bio page and want an assistant to make edits, restructure links into widgets, adjust themes or subpages, or check stats without using the web editor.
Requirements
A remote MCP endpoint at mcp.own.page over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared; an own.page account is implied by the OAuth flow.
Before you install
The server can change a live public page: edits to links, widgets, themes and subpages may be visible immediately. Access is granted through OAuth, so review which account and permissions you authorize. Tool details are not published, so confirm what each tool writes before use.

Installation

In SourceWeft

  1. Open own.page 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/page.own%2Fown-page/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": {
    "own-page": {
      "type": "http",
      "url": "https://mcp.own.page/"
    }
  }
}

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. v1.0.0LatestNov 1, 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.