Install

The server is published on npm as @micropage-sh/mcp (binary micropage-mcp). Source: github.com/micropage-sh/mcp. It needs Node.js 20 or later and a Pro or Pro+ account.

1. Log in with the CLI

The server has no login of its own. It uses the session the CLI stores in ~/.micropage/config.json.

npm install -g @micropage-sh/cli
micropage login

micropage login refuses Free accounts, so a Free account has no session to share. If you log in after the server has started, the next tool call picks up the session; no restart needed. micropage logout signs the server out as well.

For CI or other headless setups without a login, use a deploy token instead.

2. Add the server to your client

Claude Code

claude mcp add micropage -- npx -y @micropage-sh/mcp

Add -e flags before the -- to turn on opt-in tools, for example:

claude mcp add micropage -e MICROPAGE_MCP_ALLOW_SEND=1 -e MICROPAGE_MCP_SUBMISSIONS=1 -- npx -y @micropage-sh/mcp

Claude Desktop

Settings → Developer → Edit Config opens claude_desktop_config.json. Add:

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

Restart Claude Desktop afterwards.

Cursor

Add the same block to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json to make it available in every project:

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

VS Code

Add it to .vscode/mcp.json. VS Code uses a servers key:

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

Any other MCP client

The server speaks stdio. Point the client at:

npx -y @micropage-sh/mcp

or install it globally with npm install -g @micropage-sh/mcp and run micropage-mcp.

Environment variables

All optional. Set them in the client config's env block (or with -e in Claude Code).

Variable	Default	Effect
MICROPAGE_MCP_ALLOW_SEND	off	Lets publish_post publish posts that email a newsletter list. Without it, those posts are refused; web-only posts still publish.
MICROPAGE_MCP_ALLOW_DELETE	off	Registers delete_project. Without it, the tool does not exist.
MICROPAGE_MCP_SUBMISSIONS	off	Registers list_submissions, which returns form submissions (personal data). Without it, only per-form counts are available.
MICROPAGE_CONFIG_DIR	~/.micropage	Directory holding the CLI session file config.json.
MICROPAGE_DEPLOY_TOKEN	unset	A project deploy token. Set together with MICROPAGE_DEPLOY_PROJECT; see Deploy tokens.
MICROPAGE_DEPLOY_PROJECT	unset	The uuid of the project the deploy token belongs to.

The three switches accept 1, true, yes, or on. Read Safety before turning any of them on.

Example with switches in a JSON config:

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

Check that it works

Ask the assistant "Which micropage account are you connected to?". It calls whoami, which reports the email, plan, and whether it is using your login session or a deploy token. If you are not logged in, whoami says so instead of failing.

If the micropage tools are missing from the client entirely, the client did not start the server. The usual causes are Node.js older than 20, npx not on the PATH the client launches with, or the config file in the wrong place.