microservices.sh

sh.microservicesPublished by microservices.shOfficial publisherv0.1.3Updated Oct 24, 2026

MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

MCP server that lets an AI coding agent plan, validate, generate and preview-deploy Cloudflare-native apps from reusable microservices.sh modules.

What you can do
  • Discover and inspect templates, modules and module documentation
  • Compose an app plan, validate configuration and generate project files for review
  • Run readiness checks, plan adding modules, check updates and plan module upgrades
  • Check secrets status and create a preview deployment plan
  • Deploy a preview through the remote control plane and check deployment status
When to use it
Useful when an agent is building a Cloudflare app from common product modules such as auth, booking, customer records, payments, files or audit logs, and you want typed planning, validation and readiness checks before anything is deployed.
Requirements
Runs as a local stdio process (npm package @microservices-sh/mcp, installed with pnpm) or as a remote endpoint. Remote tools need a bearer token supplied via the Authorization header or the MICROSERVICES_API_KEY variable (MICROSERVICES_TOKEN as fallback); MICROSERVICES_API_URL defaults to the hosted control plane. Network access to the control plane is required for remote tools.
Before you install
The remote tools send requests to the microservices.sh control plane using your API key. deploy_preview is mutating and requires confirm set to "preview"; create_preview_plan should be run first. Keep the API key out of shared configs, and review generated project files before use.

Installation

In SourceWeft

  1. Open microservices.sh in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/sh.microservices%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "microservices-sh": {
      "type": "http",
      "url": "https://api.microservices.sh/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

@microservices-sh/mcp

[npm version] [Official MCP Registry] [mcp MCP server]

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

bash
pnpm add -D @microservices-sh/mcp

Or run it directly after publish:

bash
pnpm dlx @microservices-sh/mcp

Or install from Glama:

MCP Client Config

json
{  "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:

json
{  "mcpServers": {    "microservices-local": {      "command": "node",      "args": ["/absolute/path/to/mcp/dist/index.js"]    }  }}

Build the local package first:

bash
pnpm build

For agent-oriented one-click install guidance, see llms-install.md.

Tools

Read-only and local planning tools:

  • list_templates
  • inspect_template
  • list_modules
  • inspect_module
  • list_module_docs
  • get_module_doc
  • compose_app
  • validate_config
  • generate_project
  • run_checks
  • plan_add_module
  • check_updates
  • plan_module_upgrade
  • get_secrets_status
  • create_preview_plan

Remote control-plane tools:

  • deploy_preview
  • get_deployment_status

deploy_preview is mutating and requires confirm: "preview". Run create_preview_plan first.

Environment

VariablePurpose
MICROSERVICES_API_URLRemote control-plane URL. Defaults to https://api.microservices.sh.
MICROSERVICES_API_KEYBearer token for remote tools.
MICROSERVICES_TOKENFallback 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:

The package declares "mcpName": "sh.microservices/mcp" in package.json. Docker/OCI packaging should wrap this same stdio server rather than forking behavior.

Source: README.md at commit f87778c

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts