Pageree README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Pageree listing page.
Pageree MCP Server
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.
| Endpoint | https://mcp.pageree.com/ |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1, dynamic client registration, PKCE S256 |
| Registry name | com.pageree/landing-pages |
| Website | pageree.com |
This repository is the public home of the Pageree MCP server: its documentation and its
server.jsonregistry 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
| Tool | Purpose |
|---|---|
list_pages | List the pages in the account, with status and URLs |
get_page_information | Details for one page: slug, status, goal, delivery, domain |
save_draft | Create or update a page's draft HTML |
get_draft_html | Read back the current draft |
discard_draft | Throw away the draft and keep the published version |
publish | Put the draft live on its public URL |
list_versions | The version history of a page |
get_published_html / get_previous_version_html | Read a live or earlier version |
rollback | Restore a previous version |
audit_page | Check a page against Pageree's structure and quality rules |
Leads and goals
| Tool | Purpose |
|---|---|
set_goal | Define what the page is trying to achieve |
set_delivery | Route form submissions — email or webhook |
Form submissions from published pages are captured by Pageree and delivered to the destination you configure.
Analytics
| Tool | Purpose |
|---|---|
get_analytics | Sessions, 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
| Tool | Purpose |
|---|---|
generate_image | Generate an image for the page |
search_icons | Find an icon |
upload_asset / remove_asset / get_uploaded_page_assets | Manage the page's hosted images and files |
Custom domains
| Tool | Purpose |
|---|---|
custom_domain_set / custom_domain_status / custom_domain_remove | Serve 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:
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".
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
| Symptom | What to check |
|---|---|
| 404 or an SSE error | Use https://mcp.pageree.com/ exactly, and select Streamable HTTP. The endpoint is at the root. |
| Authentication required | Re-run your client's connect or sign-in command and finish the browser authorization. |
| No tools appear | Confirm the server is enabled and start a new agent chat after connecting. |
| Wrong account | Disconnect, reconnect, and sign in to the intended Pageree account. |
| Organization blocks the server | VS Code and some clients let an administrator restrict MCP servers; ask yours to allow mcp.pageree.com. |
Repository contents
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.