Back to Browse

Mcp MCP Server

Developer ToolsModerate7.2MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.micropage.sh/mcp

Security Report

7.2
Moderate7.2Low Risk

The micropage MCP server is a well-structured publishing tool that requires a paid account session or deploy token, and gates outward-facing actions (email sending, project deletion, form submission data) behind opt-in env switches and server-side confirmation tokens. The main caveats are that the deploy-token project pin is acknowledged as weak scoping, and the visible code is only partial (tool implementations and client modules were not provided, and the content file is truncated), so the review could not verify all network destinations or data handling. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

12 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

What You'll Need

Set these up before or after installing:

Deploy token for headless use (CI). Set together with MICROPAGE_DEPLOY_PROJECT. Without both, the server uses the session from `micropage login`.Required

Environment variable: MICROPAGE_DEPLOY_TOKEN

UUID of the project the deploy token belongs to. Required when MICROPAGE_DEPLOY_TOKEN is set.Optional

Environment variable: MICROPAGE_DEPLOY_PROJECT

Let publish_post email the newsletter subscriber list.Optional

Environment variable: MICROPAGE_MCP_ALLOW_SEND

Register the delete_project tool.Optional

Environment variable: MICROPAGE_MCP_ALLOW_DELETE

Register the form submission tools, which read visitor-entered personal data.Optional

Environment variable: MICROPAGE_MCP_SUBMISSIONS

Directory holding the CLI session (config.json). Defaults to ~/.micropage.Optional

Environment variable: MICROPAGE_CONFIG_DIR

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub 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:

npm install -g @micropage-sh/cli
micropage login
claude mcp add micropage -- npx -y @micropage-sh/mcp

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

{
  "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:

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

Reviews

No reviews yet

Be the first to review this server!