For the full documentation index, see PageWeave Documentation or fetch llms.txt.

Getting Started

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

Prerequisites

  • A PageWeave account at pageweave.dev
  • An AI agent that supports MCP (Claude Code, Cursor, Windsurf, ChatGPT, etc.)

Quick Setup

Cursor (One-Click)

Click to add PageWeave to Cursor automatically:

cursor://anysphere.cursor-deeplink/mcp/install?name=PageWeave&config=eyJ1cmwiOiJodHRwczovL3BhZ2V3ZWF2ZS5kZXYvbWNwIn0=

Or visit your dashboard for the install button.

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, and Continue.

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 opencode.json:

{
  "mcp": {
    "pageweave": {
      "type": "remote",
      "url": "https://pageweave.dev/mcp",
      "enabled": true,
      "oauth": {}
    }
  }
}

OpenCode MCP Docs ↗

Claude Code

Add to your .mcp.json:

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

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 ↗

Cursor

Add to .cursor/mcp.json:

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

Cursor MCP Docs ↗

Windsurf

Add to your mcp_config.json:

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

Windsurf MCP Docs ↗

Continue

Add to your .continue/config.json or config.yaml:

{
  "mcpServers": [
    {
      "name": "PageWeave",
      "type": "streamable-http",
      "url": "https://pageweave.dev/mcp"
    }
  ]
}

Continue 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 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, custom domain 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

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, delete_page to create versioned HTML content.

Step 5: Preview and Publish

  • Share the preview link with your client
  • Review changes in the dashboard
  • Pin the version to publish

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 bypass scope checks and provide full access. Best for CI/CD and server-to-server use.

Next Steps