microservices.sh
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
What can you do with microservices.sh?
list_templatesinspect_templatelist_modulesinspect_modulelist_module_docsget_module_doccompose_appvalidate_config
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http microservices-sh 'https://api.microservices.sh/mcp' --header 'Authorization: <Bearer ${MICROSERVICES_API_KEY}>'
{
"mcpServers": {
"microservices-sh": {
"type": "http",
"url": "https://api.microservices.sh/mcp",
"headers": {
"Authorization": "<Bearer ${MICROSERVICES_API_KEY}>"
}
}
}
}
@microservices-sh/mcpclaude mcp add microservices-sh -- npx -y @microservices-sh/mcp@0.1.3
{
"mcpServers": {
"microservices-sh": {
"command": "npx",
"args": [
"-y",
"@microservices-sh/mcp@0.1.3"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
@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.
Frequently asked questions
What is microservices.sh?
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
How do I install microservices.sh?
It runs as a remote server. In Claude Code: claude mcp add --transport http microservices-sh 'https://api.microservices.sh/mcp' --header 'Authorization: <Bearer ${MICROSERVICES_API_KEY}>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does microservices.sh need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is microservices.sh open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains microservices.sh?
It is published by microservices-sh. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.