Micropage

io.github.micropage-shv0.1.3Updated Oct 6, 2026

Create, edit and publish micropage.sh landing pages and blog posts from markup.

VerifiedStreamable HTTPWeb executableBusiness & CommerceProductivity & Workflow

Overview

AI-generated overview

Lets an assistant create, edit and publish micropage.sh landing pages and blog posts from markup, with optional email, delete and form-submission tools.

What it does
An MCP server for micropage.sh that lets an AI assistant create, edit and publish micropages and posts from markup. It works with clients such as Claude Code, Claude Desktop, Cursor and VS Code. Emailing subscribers, deleting projects and reading form submissions are off by default and must be enabled explicitly.
When to use it
Useful when you build or maintain micropage.sh landing pages and blog posts and want an assistant to draft, edit and publish them from markup. Also relevant for headless or CI publishing with a deploy token.
Requirements
Node.js 20 or later and a Pro or Pro+ micropage account. It uses the session from the micropage CLI (micropage login), or for headless use the MICROPAGE_DEPLOY_TOKEN and MICROPAGE_DEPLOY_PROJECT variables. A hosted endpoint is also available and signs in with OAuth. Optional variables: MICROPAGE_CONFIG_DIR, MICROPAGE_MCP_ALLOW_SEND, MICROPAGE_MCP_ALLOW_DELETE, MICROPAGE_MCP_SUBMISSIONS.
Before you install
The deploy token (MICROPAGE_DEPLOY_TOKEN) is a secret and is set together with MICROPAGE_DEPLOY_PROJECT. Enabling MICROPAGE_MCP_ALLOW_SEND lets publish_post email the newsletter subscriber list, MICROPAGE_MCP_ALLOW_DELETE registers the delete_project tool, and MICROPAGE_MCP_SUBMISSIONS registers tools that read visitor-entered personal data. These are off by default; enable them only when needed.

Installation

In SourceWeft

  1. Open Micropage in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.micropage.sh/mcp"
    }
  }
}

README

@micropage-sh/mcp

MCP server for micropage.sh. It lets an AI assistant (Claude Code, Claude Desktop, Cursor, VS Code) create, edit and publish micropages and posts from markup.

Documentation: https://docs.micropage.sh/docs/mcp/overview/

Install

The server needs Node.js 20 or later and a Pro or Pro+ account. It uses the session from the micropage CLI:

sh
npm install -g @micropage-sh/climicropage loginclaude mcp add micropage -- npx -y @micropage-sh/mcp

For other clients, run npx -y @micropage-sh/mcp over stdio:

json
{  "mcpServers": {    "micropage": {      "command": "npx",      "args": ["-y", "@micropage-sh/mcp"]    }  }}

Emailing subscribers, deleting projects and reading form submissions are off by default. Turn them on with MICROPAGE_MCP_ALLOW_SEND=1, MICROPAGE_MCP_ALLOW_DELETE=1 and MICROPAGE_MCP_SUBMISSIONS=1. For headless use, set MICROPAGE_DEPLOY_TOKEN and MICROPAGE_DEPLOY_PROJECT instead of logging in. See Install and Safety.

Hosted server

micropage also hosts this server at https://mcp.micropage.sh/mcp. Clients connect over streamable HTTP and sign in with OAuth through the micropage account, so nothing is installed locally. Clients register themselves on first connect; in claude.ai just add a custom connector with the URL. Claude Code:

sh
claude mcp add --transport http micropage https://mcp.micropage.sh/mcp

The setup for claude.ai and Claude Desktop, the per-connection permissions, and the deploy-token headers for headless use are in Hosted server.

Development

See DEVELOPMENT.md for working on the server and PUBLISHING.md for releases.

License

MIT

Source: README.md at commit c84c7bc

Tools

0
Tool metadata has not been indexed yet.

Version history

3
  1. v0.1.3LatestOct 5, 2026
  2. v0.1.2Oct 5, 2026
  3. v0.1.1Oct 4, 2026