Overview

info

The MCP server ships on Pro and Pro+, like the CLI. On Free, only whoami and get_markup_reference work.

Micropage ships an MCP server, @micropage-sh/mcp. Connect it to Claude Code, Claude Desktop, Cursor, VS Code, or any other MCP client, and the assistant can create projects, write .page markup, upload images, save drafts, publish, write posts, and read form data in your account.

micropage login
claude mcp add micropage -- npx -y @micropage-sh/mcp

The server runs locally over stdio, needs Node.js 20 or later, and acts as the account you logged in with through the CLI. Per-client setup is on Install.

What the assistant can do

Area	Tools
Account	whoami
Projects	list_projects, get_project, get_page_source, create_project, save_page, delete_project (opt-in)
Builds	publish_build, get_deploy_status, list_builds
Files	upload_asset, list_files, get_file_url
Forms	list_forms, list_submissions (opt-in)
Posts	list_posts, upsert_post, preview_post_send, publish_post, unpublish_post, delete_post
Reference	get_markup_reference

Arguments and behavior for each are on Tools.

How it maps to the rest of Micropage

The server works on the same projects, builds, posts, and files as the web app and the CLI. A draft the assistant saves shows up in the editor; a page you edit in the editor is what get_page_source returns next.

• Saving never publishes. save_page writes a draft build. Nothing changes on the live site until publish_build runs.
• Publishing is a separate, guarded step. publish_build, publish_post, unpublish_post, delete_post, and delete_project change what the public sees or send email. Your MCP client should ask you before each call. See Safety.
• The grammar is built in. The server bundles the .page grammar, the posts format, and the starter examples, so the assistant does not have to guess tags. See Resources and prompts.
• No local files. Tools take content inline and never read or write your project folder (upload_asset with a local path is the one exception, and it only reads). To work on a local .page checkout, use the CLI.

Custom domains are read-only here: get_project reports their status, and you change them in the editor settings.

Next

• Install: per-client configuration and environment switches.
• Tools: every tool and its key arguments.
• Safety: what is guarded, and what to approve by hand.
• Deploy tokens: headless and CI use, pinned to one project.
• Resources and prompts: the reference text and workflow prompts the server exposes.
• Recipes: what to ask for, and the tool calls it produces.