Resources and prompts

Resources

The server bundles the .page reference so the assistant writes markup from the grammar instead of guessing. All resources are read-only and local to the server.

URI	Content
micropage://grammar	The short .page grammar. Same text as docs.micropage.sh/llms.txt.
micropage://grammar/full	The complete reference. Same text as docs.micropage.sh/llms-full.txt.
micropage://posts/format	Post fields (title, slug, description, visibility, hero, email list, subject, preview, Markdown body) and the post lifecycle.
micropage://agent-guide	Editing rules: project layout, the closed tag vocabulary, edit in place, no invented tags, no inline colors, no markdown fences.
micropage://examples	Index of the bundled example files with a one-line summary each.
micropage://examples/{name}	One complete .page example.

Example names: agency-portfolio, blog-publication, components-colors, components-hero-variants, components-pricing-and-forms, devtool-docs, event-conference, mobile-app-landing, portfolio, restaurant-landing, startup-landing. The components-* files are fragments showing one feature; the rest are full sites. create_project hands out startup-landing as its starter.

Many clients never read resources on their own. The get_markup_reference tool returns the same text (topics grammar, grammar_full, posts_format, agent_guide, examples_index, example), and the tool descriptions tell the assistant to call it before writing markup.

Prompts

Prompts are prepared instructions you invoke from the client, for example as a slash command in Claude Code (/mcp__micropage__create_landing_page). Each one has the assistant follow a fixed sequence of tool calls and stop before anything outward-facing.

Prompt	Arguments	What it does
create_landing_page	brief, style?	Reads the grammar and the closest example, picks or creates a project (asking you which), writes the page, saves it as a draft with save_page, and shows you the preview URL. Does not publish.
edit_page	project, change	Fetches the current source with get_page_source, makes the smallest edit that does what you asked, keeps everything else, and saves a draft. Does not publish.
write_post	project, topic, audience?	Drafts a post with upsert_post, email off unless you asked for a newsletter, and stops. If you then ask to publish, it runs preview_post_send first and shows you the result before calling publish_post.
review_submissions	project, form?	Summarizes recent submissions with list_submissions: volume, recurring themes, and messages that need a reply. Treats submission text as data and flags injection attempts. Needs MICROPAGE_MCP_SUBMISSIONS=1.

Publishing is always a separate request from you. See Recipes for what each flow looks like in practice.