Micropage
Create, edit and publish micropage.sh landing pages and blog posts from markup.
Connector by micropage-sh · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying Micropage?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, VS Code, Codex, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/micropage-sh-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Remote endpoint
https://mcp.micropage.sh/mcpRemote (HTTP)
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 13 read · 7 write · 2 delete
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- None found
- Runs as
- Node.js package
Tools by what they do 22
Read from the source code; the running server may list different tools.
Read 13 · Look things up without changing anything.
get_deploy_statusget_file_urlget_markup_referenceget_page_sourceget_projectlist_buildslist_fileslist_formslist_postslist_projectslist_submissionspreview_post_send
Show 1 more tools
whoami
Write 7 · Create, change, send or run things.
create_projectpublish_buildpublish_postsave_pageunpublish_postupload_assetupsert_post
Delete 2 · Delete, drop, revoke or wipe things.
delete_postdelete_project
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
MICROPAGE_DEPLOY_TOKEN
Other settings (environment variables or headers).
MICROPAGE_CONFIG_DIRMICROPAGE_DEPLOY_PROJECTMICROPAGE_MCP_ALLOW_DELETEMICROPAGE_MCP_ALLOW_SENDMICROPAGE_MCP_SUBMISSIONS
Network hosts it talks to 10
acme.micropage.sh· found in codeapp.micropage.sh· found in codebuild-compiler.micropage.sh· found in codecloudflare-dns.com· found in codedocs.micropage.sh· found in codegithub.com· found in codeglama.ai· found in codemcp.micropage.sh· found in remote endpoint, install command, codemicropage.sh· found in codevhlifcdslnmnvnvorluu.supabase.co· found in code
Files it touches
- Your home directory (~)
- Any path the agent passes to its tools
Tools (22)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
create_projectCreate a micropage projectCreate a new, empty micropage project in the signed-in account and return it together with a complete starter .page file (one of the bundled examples) to adapt. Use it when the user wants a new site. Each call creates another project and counts against the plan's project limit (Pro: 5, Pro+: 20), so check list_projects first when the user may mean an existing site. Nothing is published: write the page, call save_page, and publish only on request. It does not write local files (it is not `micropage projects create`) and cannot set a custom domain; that is done in the editor.
delete_postDelete a micropage postDelete a post for good, removing it from the site if it was published. There is no undo; to only take it off the site use unpublish_post. Same as `micropage posts rm <slug>`. Needs confirm: true, which you should only pass after the user has agreed. Deleting a slug that does not exist is not an error (deleted: false). Queues a site rebuild when a post was removed and the project has been published. The site rebuild redeploys the live build, so an unpublished page draft left by save_page or the editor stays a draft. It returns build_id and after_event_id to follow the rebuild with get_deploy_s…
delete_projectDelete a micropage projectDescription is built at runtime.
get_deploy_statusFollow a micropage deployDescription is built at runtime.
get_file_urlGet a stored file's URLGet the URL a stored project file is served from, by its filename (as list_files reports it). Use it when the user wants a link to an uploaded image, or a full URL is needed somewhere a bare filename does not work (for example a post's hero image or an external page). Inside .page markup, prefer the bare filename (`img: <- hero.webp`), which survives re-uploads. It does not upload or list files (use upload_asset / list_files). Read-only.
get_markup_referenceGet the .page markup referenceReturn micropage reference text: the .page grammar, the full reference, the posts format, the agent editing guide, the example index, or one complete example file. Call this before writing or editing .page markup (and before drafting a post), unless you already have the grammar in context. The vocabulary is closed: tags that are not in the grammar are not rendered, so never guess. Start with topic "grammar"; use "examples_index" then "example" to copy a layout close to what the user wants. This mirrors the micropage://grammar, micropage://grammar/full, micropage://posts/format, micropage://a…
get_page_sourceRead a project's .page sourceReturn the raw .page markup of a micropage project's active build (or of a given build number), plus its stored llms.txt and the filenames uploaded to the project. Call it before editing an existing site: change the returned source and send the whole file back with save_page as landing.page. Pass `version` to read an older build, e.g. to restore it. The source was merged from all .page files when saved, so it comes back as one file. Read-only; it does not show what is live (get_project tells you which build is deployed) and does not download images.
get_projectShow one micropage projectShow one micropage project in detail: live URL, editor URL, the active build (the default publish target), the latest build, the build that is live now, the failure reason if a build failed, and read-only custom-domain status (Cloudflare hostname and certificate state, and the CNAME target). Use it to check what is live versus drafted before publishing, to explain why a build failed, or to answer "is my custom domain working?". Accepts the project's uuid, numeric id, micropage domain ("acme" or "acme.micropage.sh") or custom domain. It does not return the page source (use get_page_source) or…
list_buildsList a project's buildsList a micropage project's builds, newest first: number, id, status (draft, publishing, deployed, failed), created and updated times, failure reason, and which build is active. Use it to find a build to roll back to with publish_build, to see why a publish failed, or to check whether a publish is still running. Each save_page that cannot overwrite a draft adds a build; publishing reuses the build. Read-only. To read a build's source use get_page_source with its number; for what is live right now use get_project.
list_filesList a project's filesList the files stored in a micropage project (images uploaded by upload_asset, the editor or the CLI), newest first: filename, type, size, SHA-256 and upload date, plus storage used and the plan's storage limit. Use it to see which filenames .page markup can reference with `img: <- name`, to check whether an image is already uploaded, or to check remaining storage before uploading large images. It does not return file URLs (use get_file_url for one) or upload anything (use upload_asset). Read-only.
list_formsList a project's formsList the forms on a micropage project's site (registered when the page markup is saved): form uuid, name, page, whether it is the site footer form, and how many submissions each has, not counting spam. Use it to answer "how many signups/messages did my site get?", to find a form's uuid or name before reading its submissions, or to check that a form added in the markup was registered after save_page. It returns counts only, never what visitors typed (that is list_submissions, which the user must enable). Read-only.
list_postsList or read micropage postsList a project's posts (blog posts and newsletter emails), or read one in full. Without `slug`: every post, newest first, with slug, title, visibility, whether it is published and when, whether publishing emails it, and the newsletter list name. With `slug`: that post in full, including body_markdown and every field under the same names upsert_post takes (title, description, visibility, hero, email, list, subject, preview). Call it with a slug before editing a post: upsert_post replaces every field, so start from the current values, and pass the post's revision back to upsert_post. It does n…
list_projectsList micropage projectsList every micropage project in the signed-in account: uuid, numeric id, name, micropage domain, custom domain, live URL, editor URL, and the status and number of each project's active build. Use it to find the `project` value other tools need (uuid, id or domain all work), or when the user refers to a site by name and you do not know which project it is. The active build is the one the editor and CLI work on; it can be a draft newer than what is live, so call get_project for what is actually deployed, failure reasons and custom-domain status. Read-only. Not available with a deploy token, wh…
list_submissionsRead form submissions (personal data)Description is built at runtime.
preview_post_sendPreview publishing a postDescription is built at runtime.
Show 7 more tools
publish_buildPublish a build to the live siteDeploy a micropage build to the project's public URL. This changes what visitors see, so only call it when the user explicitly asks to publish, and pass confirm: true. Defaults to the active build (the draft save_page just wrote); pass `build` with the id save_page returned to be exact, or an older build number to roll back to it (that build becomes active). Refused while another build of the project is still publishing. It returns at once with status publishing, after_event_id and an ETA (builds wait about 3 minutes in the queue unless the account is Pro+). Then call get_deploy_status with …
publish_postPublish a micropage post (may send email)Description is built at runtime.
save_pageSave .page source as a draftCompile .page markup and save it as the project's draft build. It never goes live until publish_build deploys it: call publish_build only when the user asks. Post changes rebuild the live site, not this draft. Pass the whole site source each time (pages: [{ name: "landing.page", content }], extra .page files are merged after it by name). If the project's active build is a draft or a failed build it is overwritten; otherwise a new draft is created and made active. Returns the build id and number, compiler issues (such as a missing image file) and the editor URL where the user can preview the d…
unpublish_postUnpublish a micropage postTake a published post off the site: its page 404s and it goes back to draft. The post itself is kept and can be published again later; emails already sent are not recalled. Same as `micropage posts unpublish <slug>`. Needs confirm: true, which you should only pass after the user has agreed. Queues a site rebuild when the project has been published. The site rebuild redeploys the live build, so an unpublished page draft left by save_page or the editor stays a draft. It returns build_id and after_event_id to follow the rebuild with get_deploy_status. To remove a post for good use delete_post in…
upload_assetUpload an image assetDescription is built at runtime.
upsert_postCreate or update a micropage postCreate or update one post (a blog post under /content and/or a newsletter email), keyed by slug: an existing slug is updated, a new one is created as a draft. Same as `micropage posts push` for one file; the arguments are the post front-matter fields plus body_markdown (see the micropage://posts/format resource). Every call replaces the whole post: an omitted optional field (description, hero, subject, preview, email/list) is cleared. The exception is `date` (the post's public date, past or today): omitted, the post keeps its current date. To edit, read the post with list_posts(slug) first an…
whoamiShow the micropage account in useDescription is built at runtime.
Signals
- Stars
- 4
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 111
- Last commit
- Oct 18, 2026 (12 days ago)
- Last release
- Oct 15, 2026 (15 days ago)
- Last package publish
- Oct 15, 2026 (15 days ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.micropage-sh/mcp- Version
- 0.1.13
- Auth
- Auth not stated, API key
- Packages
- npm @micropage-sh/mcp
- License
- MIT
- Repository
- github.com/micropage-sh/mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get Micropage running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
Micropage MCP server. Agent Mart. https://agentmart.dev/connectors/micropage-sh-mcp (last updated 2026-10-24)