PageWeave

dev.pageweavePublished by pageweave.devOfficial publisherv1.0.0Updated Oct 24, 2026

Agent-native website builder: create, edit, and host websites via MCP

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Agent-native website builder that lets an assistant create, edit and host websites through a remote MCP endpoint.

What you can do
  • Create new websites from an assistant conversation
  • Edit existing site content and pages
  • Host and publish the resulting sites
  • All actions run through the hosted PageWeave service over a remote MCP connection; no tool list is published, so exact operations are not documented here.
When to use it
Useful when you want an assistant to build or revise a website end to end, including hosting, without setting up local tooling. Less suitable if you need a documented, granular tool surface or offline work.
Requirements
A remote MCP connection to the PageWeave endpoint over streamable HTTP, plus OAuth sign-in to a PageWeave account. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your PageWeave account, and the assistant can create, edit and publish public websites on your behalf. Review generated content before publishing, and check the provider's terms for hosting and data handling.

Installation

In SourceWeft

  1. Open PageWeave 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/dev.pageweave%2Fpageweave/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": {
    "pageweave": {
      "type": "http",
      "url": "https://pageweave.dev/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. v1.0.0LatestSep 29, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.