@microservices-sh/mcp
OfficialThe @microservices-sh/mcp server provides AI agents with a typed planning layer for discovering, composing, validating, generating, and deploying Cloudflare-native apps using reusable microservices.sh modules.
Template & Module Discovery
list_templates/inspect_template– Browse and deep-dive into available app templates (e.g.,booking-sveltekit)list_modules/inspect_module– Discover and inspect verified building-block modules (auth, booking, payment, etc.) including their contracts, permissions, hooks, events, and storage needs
Documentation
list_module_docs/get_module_doc– List and retrieve LLM-readable documentation pages with implementation guidance, rules, and agent notes
Local Planning & Validation (read-only, no file writes)
compose_app– Compose a template + modules into a checked app contract and lockfile planvalidate_config– Validate template, module list, and configuration before generationgenerate_project– Generate project source files in memory for agent inspection without touching the filesystemrun_checks– Run local contract and readiness checks to verify module compatibility and operational guardrailsget_secrets_status– Report required secret names and configured/missing status without exposing valuescreate_preview_plan– Build a local preview-deployment readiness plan (resources, checks, warnings, approval steps) without mutating remote state
Module Lifecycle Management
plan_add_module– Plan an approval-gated module addition, reporting lockfile changes and review gatescheck_updates– Compare locked module versions against the registry to identify available updatesplan_module_upgrade– Plan a version upgrade and report approval gates, compatibility notes, and lockfile impact
Remote Deployment (mutating, requires API key)
deploy_preview– Trigger a remote preview deployment via the microservices.sh control plane (requiresconfirm: "preview"and prior plan review)get_deployment_status– Poll a remote preview deployment's status, errors, and metadata
Allows to build and deploy Cloudflare-native applications with verified modules, local checks, and approval-gated deploy plans.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@microservices-sh/mcplist available templates for a new project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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.
Related MCP server: komodo-mcp
Install
pnpm add -D @microservices-sh/mcpOr run it directly after publish:
pnpm dlx @microservices-sh/mcpOr 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 buildFor 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 |
| Remote control-plane URL. Defaults to |
| Bearer token for remote tools. |
| 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:
MCP Registry:
sh.microservices/mcpGlama:
@microservices-sh/mcpawesome-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.
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/microservices-sh/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server