About microservices.sh
microservices.sh is a standalone stdio MCP server for coding agents that build Cloudflare-native apps from reusable modules. It supports planning and validation through to project generation and approval-gated preview deployment.
Key features
- 01Discover templates and modules
- 02Inspect module contracts and docs
- 03Compose and validate app plans
- 04Generate project files and run checks
- 05Plan and deploy preview releases
Use cases
- 01Build Cloudflare apps from common product modules
- 02Check configuration before generating a project
- 03Prepare a preview deployment for approval
MCP support
Exposes planning, validation, project-generation, checks, and deployment tools to MCP clients. Preview deployment is a mutating operation that requires confirmation.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.microservices.sh/mcpclaude mcp add --transport http sh-microservices https://api.microservices.sh/mcp{"mcpServers":{"sh-microservices":{"type":"http","url":"https://api.microservices.sh/mcp"}}}Open in Cursor{"servers":{"sh-microservices":{"type":"http","url":"https://api.microservices.sh/mcp"}}}Open in VS Code{"mcpServers":{"sh-microservices":{"type":"http","url":"https://api.microservices.sh/mcp"}}}{"mcpServers":{"sh-microservices":{"serverUrl":"https://api.microservices.sh/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://api.microservices.sh/mcpAuth requiredTools
Details
From the project README@microservices-sh/mcp
MCP server for AI agents that generate, verify, and deploy Cloudflare-native apps from reusable microservices.sh modules.
This package is a standalone stdio MCP server. It vendors a small microservices.sh SDK/module-contract snapshot until the public SDK is split out.
Why Agents Use It
@microservices-sh/mcp gives coding agents a typed planning layer for building production-oriented Cloudflare apps. Agents can discover verified templates and modules, inspect module contracts, compose an app plan, validate configuration, generate project files for review, run readiness checks, and prepare approval-gated preview deployments through the microservices.sh control plane.
It is useful when an agent needs to build apps with common product modules such as auth, booking, customer records, payments, files, and audit logs without inventing each integration from scratch.
Install
pnpm add -D @microservices-sh/mcp
Or run it directly after publish:
pnpm dlx @microservices-sh/mcp
Or install from Glama:
MCP Client Config
{
"mcpServers": {
"microservices": {
"command": "microservices-mcp",
"env": {
"MICROSERVICES_API_URL": "https://api.microservices.sh",
"MICROSERVICES_API_KEY": "favored-secret-manager-reference"
}
}
}
}
For local development inside this repo:
{
"mcpServers": {
"microservices-local": {
"command": "node",
"args": ["/absolute/path/to/mcp/dist/index.js"]
}
}
}
Build the local package first:
pnpm build
For agent-oriented one-click install guidance, see llms-install.md.
Tools
Read-only and local planning tools:
list_templatesinspect_templatelist_modulesinspect_modulelist_module_docsget_module_doccompose_appvalidate_configgenerate_projectrun_checksplan_add_modulecheck_updatesplan_module_upgradeget_secrets_statuscreate_preview_plan
Remote control-plane tools:
deploy_previewget_deployment_status
deploy_preview is mutating and requires confirm: "preview". Run create_preview_plan first.
Environment
| Variable | Purpose |
|---|---|
MICROSERVICES_API_URL | Remote control-plane URL. Defaults to https://api.microservices.sh. |
MICROSERVICES_API_KEY | Bearer token for remote tools. |
MICROSERVICES_TOKEN | Fallback bearer token. |
Secret values are never returned by the MCP tools.
Registry Notes
The package is published to npm, listed in the official MCP Registry, and verified by Glama:
- npm:
@microservices-sh/mcp - MCP Registry:
sh.microservices/mcp - Glama:
@microservices-sh/mcp - awesome-mcp-servers: PR #8249
- Remote endpoint:
https://api.microservices.sh/mcp
The package declares "mcpName": "sh.microservices/mcp" in package.json. Docker/OCI packaging should wrap this same stdio server rather than forking behavior.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.