Micro skill and MCP server

The official agent-facing package for Micro. It teaches a coding harness how to build, verify, preview, deploy, diagnose, update, and roll back a full-stack Micro, then exposes the same operations as typed local MCP tools backed by micro-cli.

Micro does not receive prompts or call a model. The skill runs in the creator's existing harness; the MCP server invokes the public CLI without handling passwords or provider secrets.

Install

Install the Micro capabilities the project needs on Linux:

curl -fsSL https://micro.do/install | sh -s -- cli # CLI only
curl -fsSL https://micro.do/install | sh -s -- runtime # + local runner
curl -fsSL https://micro.do/install | sh -s -- abla # + Abla toolchain
micro doctor

Static sites and Wasm produced by Rust or another compatible toolchain do not require Abla. On macOS, brew install microdotdo/tap/micro provides the complete managed setup.

Use the setup for your coding harness. Each command runs the bundled stdio server locally and delegates deployment to the authenticated Micro CLI.

Codex

Install the skill globally:

npx skills add microdotdo/micro-mcp --skill micro-sites -g -a codex -y

Add the local MCP tools:

codex mcp add micro -- npx -y @microdotdo/micro-mcp
codex mcp list

Claude Code

Install the skill globally:

npx skills add microdotdo/micro-mcp --skill micro-sites -g -a claude-code -y

Add the local MCP tools:

claude mcp add --transport stdio --scope user micro -- npx -y @microdotdo/micro-mcp
claude mcp list

Cursor

Install the skill globally:

npx skills add microdotdo/micro-mcp --skill micro-sites -g -a cursor -y

For the local MCP tools, save this as ~/.cursor/mcp.json:

{
"mcpServers": {
"micro": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@microdotdo/micro-mcp"]
}
}
}

Pi

Pi intentionally does not provide native MCP support. Install the skill bundled with this package so Pi can follow the same Micro CLI workflow:

pi install npm:@microdotdo/micro-mcp

Or install only the skill:

npx skills add microdotdo/micro-mcp --skill micro-sites -g -a pi -y

Authenticate interactively after installation. Set MICRO_CLI only when the executable is not on PATH; it must be an executable path, never a shell command.

For repository deployment, use micro_github_link once from an authenticated owner workstation, commit the generated non-secret micro.github.json, and deploy through the first-party microdotdo/micro-action. The Action uses GitHub OIDC; no long-lived Micro credential belongs in GitHub.

For destructive project retirement, inspect and export the linked project first, then use micro_project_delete with its exact slug and confirm: true. Track the asynchronous cleanup with micro_project_deletions; local source is never removed.

For record recovery, inspect micro_backups immediately before acting. A restore requires the exact backup digest and fresh current-record digest; it replaces records only and never rewinds users, purchases, entitlements, products, files, deployments, or local source.

Project operation tools cover roles and invitations, private visibility, custom-domain proof, plan usage, spending caps, and hosted platform billing. Durable schedule tools list, configure, manually enqueue, and remove authenticated schedule.triggered events for the active production deployment. The read-only email tool reports owner-authorized quota and delivery state for verified-user notifications without exposing message bodies or credentials. The public platform-status tool separates a Micro-wide incident from a linked project failure before a harness changes or rolls back user code. Public gallery and local remix tools let a harness select one reviewed, licensed immutable source snapshot, restore it with provenance, remove the source slug, and rebuild it without creating a project or reserving anything. Invitation acceptance and private-grant creation intentionally remain secure CLI handoffs so bearer tokens never enter MCP or model context.

Develop

npm ci
npm run check
npm run build
npm test

The package uses MCP 2026-07-28 through the stable TypeScript SDK v2 stdio entry and also serves legacy clients through SDK negotiation.