MCP server for micropage.sh: let an AI assistant create, edit and publish micropages from markup.
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
MICROPAGE_DEPLOY_TOKENAPI keyoptionalDeploy token for headless use (CI). Set together with MICROPAGE_DEPLOY_PROJECT. Without both, the server uses the session from `micropage login`.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
whoamiNo description publishedThis tool published no description. Forge does not invent one.
publish_buildNo description publishedThis tool published no description. Forge does not invent one.
get_deploy_statusNo description publishedThis tool published no description. Forge does not invent one.
list_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…List 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…
No input schema was published for this tool.
upload_assetprivilegedNo description publishedThis tool published no description. Forge does not invent one.
list_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…List 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…
No input schema was published for this tool.
get_file_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 t…Get 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 t…
No input schema was published for this tool.
list_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 bef…List 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 bef…
No input schema was published for this tool.
list_submissionsNo description publishedThis tool published no description. Forge does not invent one.
list_postsNo description publishedThis tool published no description. Forge does not invent one.
upsert_postNo description publishedThis tool published no description. Forge does not invent one.
preview_post_sendNo description publishedThis tool published no description. Forge does not invent one.
publish_postNo description publishedThis tool published no description. Forge does not invent one.
unpublish_postNo description publishedThis tool published no description. Forge does not invent one.
delete_postprivilegedNo description publishedThis tool published no description. Forge does not invent one.
list_projectsNo description publishedThis tool published no description. Forge does not invent one.
get_projectNo description publishedThis tool published no description. Forge does not invent one.
get_page_sourceNo description publishedThis tool published no description. Forge does not invent one.
create_projectNo description publishedThis tool published no description. Forge does not invent one.
save_pageNo description publishedThis tool published no description. Forge does not invent one.
delete_projectprivilegedNo description publishedThis tool published no description. Forge does not invent one.
get_markup_referenceNo description publishedThis tool published no description. Forge does not invent one.
4 of 22 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for micropage.sh: let an AI assistant create, edit and publish micropages from markup.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.