Pageree

com.pagereePublished by pageree.comOfficial publisherv1.0.1Updated Oct 24, 2026

Build, publish, capture leads from, measure and improve landing pages from your AI assistant.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & CommerceMedia & Design

Overview

AI-generated overview

Pageree is a hosted MCP server that lets an assistant build, publish, measure and improve landing pages, including lead capture and analytics.

What you can do
  • List, inspect, draft, publish, version and roll back landing pages, and audit them against quality rules
  • Set page goals and route form submissions to email or a webhook
  • Read visitor analytics, including per-section clicks, exits and dwell time
  • Generate images, search icons and manage uploaded page assets
  • Attach, check or remove a custom domain
  • Load Pageree's built-in guidance on page structure, copywriting, analytics and policy, and check the connected account
When to use it
Useful when you want an assistant to create and host a landing page end to end, collect and route leads from its forms, and then revise the page based on real visitor behaviour rather than guesswork.
Requirements
A remote MCP client that supports Streamable HTTP with OAuth (for example VS Code with GitHub Copilot, Claude, Cursor or Gemini CLI), a Pageree account, and network access to the hosted endpoint. No install or API key is needed; sign-in happens in the browser. Usage is subject to your Pageree plan.
Before you install
Publishing makes a page publicly reachable, and rollback, discard and asset removal change live content, so review previews and confirm before approving. Form submissions are captured by Pageree and forwarded to the email or webhook destination you configure, and published pages carry Pageree's own first-party tracking. The service is closed source and hosted, so page content and analytics data go to a third party.

Installation

In SourceWeft

  1. Open Pageree 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/com.pageree%2Flanding-pages/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": {
    "pageree": {
      "type": "http",
      "url": "https://mcp.pageree.com/"
    }
  }
}

README

Pageree MCP Server

[Pageree]

Build, publish, capture leads from, measure and improve landing pages — from your AI assistant.

Pageree is a hosted remote MCP server. Connect it to an MCP client and your assistant can design a landing page, host it on a real URL, collect form submissions, read visitor analytics, and revise the page against what the numbers show. There is nothing to install and no API key to paste: authentication is OAuth, handled in the browser by your client.

Endpointhttps://mcp.pageree.com/
TransportStreamable HTTP
AuthenticationOAuth 2.1, dynamic client registration, PKCE S256
Registry namecom.pageree/landing-pages
Websitepageree.com

This repository is the public home of the Pageree MCP server: its documentation and its server.json registry manifest. The server itself is hosted by Pageree and its implementation is not open source, so there is no source tree here to build or run.

What it does

Pageree is built around one workflow — discover → build → publish → measure → improve — and the tools follow it.

Pages

ToolPurpose
list_pagesList the pages in the account, with status and URLs
get_page_informationDetails for one page: slug, status, goal, delivery, domain
save_draftCreate or update a page's draft HTML
get_draft_htmlRead back the current draft
discard_draftThrow away the draft and keep the published version
publishPut the draft live on its public URL
list_versionsThe version history of a page
get_published_html / get_previous_version_htmlRead a live or earlier version
rollbackRestore a previous version
audit_pageCheck a page against Pageree's structure and quality rules

Leads and goals

ToolPurpose
set_goalDefine what the page is trying to achieve
set_deliveryRoute form submissions — email or webhook

Form submissions from published pages are captured by Pageree and delivered to the destination you configure.

Analytics

ToolPurpose
get_analyticsSessions, click and bounce rates, scroll and reading behaviour, and per-section click, exit and dwell distribution

Pageree injects its own first-party tracking into published pages and attributes behaviour to individual page sections, so an assistant can tell which part of a page is losing visitors rather than only that the page is.

Assets and media

ToolPurpose
generate_imageGenerate an image for the page
search_iconsFind an icon
upload_asset / remove_asset / get_uploaded_page_assetsManage the page's hosted images and files

Custom domains

ToolPurpose
custom_domain_set / custom_domain_status / custom_domain_removeServe a page from your own domain

Built-in guidance

A set of get_skill_* tools returns Pageree's own instructions to the assistant on demand — page structure and required markup, conversion copywriting, reading analytics, the optimisation loop, image handling, form management, custom domains, privacy and consent, and content policy. The assistant loads the relevant one before it works, so page-building guidance stays current without you maintaining local rules or skill files.

whoami reports the connected account; get_subprocessors returns the current subprocessor list.

Requirements

  • An MCP client that supports remote servers over Streamable HTTP with OAuth — VS Code with GitHub Copilot, Claude, ChatGPT, Cursor, Codex, Claude Code, Gemini CLI, Windsurf, Cline, or OpenCode.
  • A Pageree account.
  • Network access to https://mcp.pageree.com/.

Service usage is subject to your Pageree plan.

Configure

VS Code (GitHub Copilot)

Add the server from the Command Palette — MCP: Add Server → HTTP — and enter https://mcp.pageree.com/. Or create .vscode/mcp.json in your workspace, merging with any servers already there:

json
{  "servers": {    "pageree": {      "type": "http",      "url": "https://mcp.pageree.com/"    }  }}

Start the server, then complete the Pageree sign-in that opens in your browser and approve the access request. Pageree's tools become available in agent mode.

Other clients

Most clients take the same two values — the URL and the Streamable HTTP transport. The transport field differs by client: Gemini CLI uses httpUrl, VS Code uses "type": "http", and Cline uses "type": "streamableHttp".

json
{  "mcpServers": {    "pageree": {      "url": "https://mcp.pageree.com/"    }  }}

Per-client walkthroughs are at pageree.com/docs.

The endpoint ends at /. Do not append /mcp or /sse.

Verify the connection

In a new agent chat:

Use Pageree to call whoami and list_pages. Do not create, change, or publish anything.

You should see the connected account and its pages. An empty list is expected on a new account.

Use it

Build a page

Create a landing page for my accounting service with a quote-request form. Ask me about the business, the audience, and the action I want first, then show me a preview before publishing.

Capture the leads

Send new enquiries from this page to my email.

Improve it with real data

Review visitor engagement on my landing page, tell me which section is losing people, and propose one change. Wait for my approval before editing or publishing.

Publishing makes a page public. Review the preview and confirm the destination before asking an assistant to publish.

Troubleshooting

SymptomWhat to check
404 or an SSE errorUse https://mcp.pageree.com/ exactly, and select Streamable HTTP. The endpoint is at the root.
Authentication requiredRe-run your client's connect or sign-in command and finish the browser authorization.
No tools appearConfirm the server is enabled and start a new agent chat after connecting.
Wrong accountDisconnect, reconnect, and sign in to the intended Pageree account.
Organization blocks the serverVS Code and some clients let an administrator restrict MCP servers; ask yours to allow mcp.pageree.com.

Repository contents

text
README.md            This documentserver.json          MCP registry manifest for com.pageree/landing-pagesassets/logo.svg      Pageree logo

No executable code, server runtime, or credentials are distributed here. Tool calls go to the hosted Pageree service; your client stores its own OAuth credentials.

Links

Source: README.md at commit a0ef52c

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

2
  1. v1.0.1LatestSep 23, 2026
  2. v1.0.0Sep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.