The Pagenflow MCP server connects Claude, Claude Code, Cursor, or any MCP-compatible agent to your account. Create projects, build and validate email templates, and send test emails in plain language, with no local install.
claude mcp add --transport http pagenflow https://mcp.pagenflow.workers.devClaude Code one-liner. Other clients are in the setup steps below.
The Model Context Protocol (MCP) is the open standard that lets an AI assistant call real apps. Pagenflow exposes your account as tools: say it in plain language and it happens, with exactly the permissions you already have.
Build, validate, publish and export (HTML, React, Shopify Liquid), send test emails, and generate preview screenshots.
Create, star, archive, duplicate and publish projects.
Invite teammates, change roles, switch workspace.
Brand colors, typography tokens and logos, kept in sync.
Browse and manage the blocks your team shares.
Check your plan and credit balance before you kick off a batch of exports or test sends.
Review connected integrations and manage your test-send recipient pool.
Not covered yet: the drag-and-drop canvas itself, connecting a brand-new third-party integration, and completing a billing checkout. Those still need a browser session.
Three steps to a hosted MCP server: nothing to install or keep running.
Go to Account Settings → API Tokens, name it (e.g. “Claude Desktop”) and copy it. It's shown only once, and grants the same access as signing in, so keep it only in your AI client's config.
Pick your client and paste the same URL and token everywhere. It speaks standard Streamable HTTP.
Settings → Developer → Edit Config
{
"mcpServers": {
"pagenflow": {
"url": "https://mcp.pagenflow.workers.dev",
"headers": {
"Authorization": "Bearer pfmcp_live_your_token_here"
}
}
}
}Try “list my Pagenflow teams” or “create a project called Onboarding Emails”. Your assistant discovers the tools on its own and only sees the ones your account may use.
Every tool is named and scoped by domain, so your assistant picks the right one every time.
A token can only do what its owner can do in the app. Revoke it any time from account settings.
A hosted Streamable HTTP server. Point your client at a URL, with no local process to keep running.
Everything you need to know about using Pagenflow through MCP.
MCP is an open standard that lets AI assistants like Claude connect securely to external tools and data sources. Instead of copy-pasting between an app and a chat window, an MCP-compatible assistant can call a defined set of "tools" directly — in Pagenflow's case, that means creating projects, managing templates, inviting teammates, and dozens of other actions.
A personal access token grants the same access as signing in — treat it like a password. You generate and revoke tokens yourself from Account Settings → API Tokens, and revoking one takes effect immediately. We recommend giving each MCP client (e.g. "Claude Desktop", "Claude Code") its own token so you can revoke one without affecting the others.
Not yet. The MCP server covers everything around a template — creating, organizing, publishing, exporting, testing, and screenshotting it — but the drag-and-drop design itself still happens in Pagenflow's editor. Support for AI-driven visual editing is on our roadmap.
Any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Codex, Kimi, and other agent frameworks that support the Streamable HTTP MCP transport. You connect by adding our server's URL and your personal access token to the client's configuration — no local install required.
Yes — an MCP tool call that would cost credits in the app (like exporting a template or sending a test email) costs the same via MCP. Read-only actions, like listing projects or checking your credit balance, are always free.
Generate a token, paste one command, and start managing your email templates in plain language. Revoke access any time.
claude mcp add --transport http pagenflow https://mcp.pagenflow.workers.devNo local install · Works with Claude, Cursor, Windsurf, Cline, Codex & Kimi