PageWeave / Docs

Overview

Markdown

Getting Started

Connect your AI agent to PageWeave and start building websites in minutes.

Fastest path: paste pageweave.dev/setup into your agent — it fetches the setup guide and configures itself. The manual steps below are the fallback.

Prerequisites

  • A PageWeave account — early access is by invitation. Use an invite code at pageweave.dev/create-account for instant access, or request an invite
  • An AI agent that supports MCP (Claude Code, ChatGPT (Codex), OpenCode, Windsurf / Devin Desktop, etc.)

Quick Setup

Claude Code (One Command)

claude mcp add --transport http --scope user pageweave https://pageweave.dev/mcp

Other Clients

See the manual configuration below for OpenCode, Claude Desktop, Windsurf / Devin Desktop, and ChatGPT (Codex).

Step 1: Configure Your MCP Client

PageWeave supports automatic OAuth 2.1 authentication. Just add the MCP endpoint URL to your client — no API key needed. On first connection, your browser will open for authorization.

OpenCode

Add to your global ~/.config/opencode/opencode.jsonc:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "pageweave": {
        "type": "remote",
        "url": "https://pageweave.dev/mcp"
      }
    }
  }
}

Or run opencode mcp add pageweave --global --url https://pageweave.dev/mcp.

OpenCode MCP Docs ↗

Claude Code

Add to your .mcp.json:

{
  "mcpServers": {
    "pageweave": {
      "type": "http",
      "url": "https://pageweave.dev/mcp"
    }
  }
}

Claude Code does not open the browser on its own: run /mcp, select pageweave, and choose Authenticate.

Claude Code MCP Docs ↗

Claude Desktop

Claude Desktop's config file is stdio-only — use the mcp-remote bridge to connect to PageWeave's HTTP endpoint:

{
  "mcpServers": {
    "pageweave": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://pageweave.dev/mcp"]
    }
  }
}

Alternative: Use Settings → Connectors → Add custom connector and enter https://pageweave.dev/mcp directly.

Claude Desktop Auth Docs ↗

Windsurf / Devin Desktop

Add to the user-level MCP config ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows):

{
  "mcpServers": {
    "pageweave": {
      "url": "https://pageweave.dev/mcp"
    }
  }
}

With the Devin CLI installed, devin mcp add -s user pageweave https://pageweave.dev/mcp does the same (without -s user it defaults to project-local scope).

Devin Desktop MCP Docs ↗

ChatGPT (Codex)

CLI or IDE extension:

codex mcp add pageweave --url https://pageweave.dev/mcp

In the ChatGPT desktop app: Settings → MCP servers → Add server, URL https://pageweave.dev/mcp. If the sign-in flow does not open on first use, run codex mcp login pageweave, or select Authenticate in the app's MCP server list.

Codex MCP Docs ↗

Step 2: Authorize

When your client first connects to PageWeave, it will prompt you to sign in through your browser. This happens automatically — no manual token management required.

The client handles the full OAuth flow: discovery, dynamic client registration, PKCE authorization, token exchange, storage, and automatic refresh.

Step 3: Create Your First Website

Tell your agent:

Create a website for my bakery called "Sweet Crumbs"

The agent will use list_websites, get_website, create_website, update_website to set up the site with a subdomain like sweet-crumbs.pageweave.site.

Everything You Need, Nothing You Don't

PageWeave is all-in-one. You don't need external tools for hosting, databases, or deployment.

What's Included

  • Hosting — Your site is live immediately at your-site.pageweave.site
  • Database — Built-in data tables for structured content (blogs, products, events)
  • DNS & SSL — Automatic SSL certificates, hostname support
  • Forms — Working contact forms with spam protection and email notifications
  • Analytics — Privacy-first visitor stats, no cookies or trackers
  • Assets — Image optimization, font hosting, file storage
  • Versioning — Every change is versioned, roll back anytime
  • Environments & Releases — Dev/staging preview surfaces and immutable release snapshots

What You Don't Need

❌ No GitHub — No git repository required
❌ No Vercel/Netlify — No external hosting or deployment pipeline
❌ No Neon/PlanetScale — No external database service
❌ No separate DNS provider — PageWeave handles DNS management
❌ No build tools — No npm, webpack, or deployment scripts

Your AI agent builds directly on PageWeave. The site is live immediately. No deploy step, no external services, no configuration headaches.

Step 4: Build Pages

Create a home page, menu page, and contact page

The agent uses list_pages, get_page, create_page, update_page, and discard_page to create versioned HTML content. Discarded pages disappear immediately and remain restorable for 30 days (see Deleting & Restoring Content).

Step 5: Preview and Publish

  • Create a dev/staging environment for review — every website gets additional dev/staging environments (up to 1,000) (create_environment, host *.env.pageweave.site; noindex, no analytics)
  • Draft table rows render on dev environments on template pages, so you can review unpublished content
  • Release & go live when ready: create_release snapshots all content versions; update_environment release freezes the environment to it. Every release has a *.r.pageweave.site permalink, kept while the release is retained, for sharing with your client
  • Roll back anytime by attaching an older release — releases are immutable snapshots, nothing is overwritten

Alternative: API Key Authentication

For programmatic access or clients that don't support OAuth, use API keys:

  1. Create an API key in your dashboard settings
  2. Pass it via the Authorization: Bearer <key> header

API keys carry coarse read / write scopes — create a read-only key for CI/CD and server-to-server use.

Next Steps