In-depth architectural comparison of the Microservices Sh MCP and UI5 MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Microservices Sh MCP
Developer Tools · Remote HTTP/SSE
Quality: 60/100 (Good) | Auth: API Key required
UI5 MCP Server
Developer Tools · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Microservices Sh MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose UI5 MCP Server if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Microservices Sh MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: MICROSERVICES_API_URL, MICROSERVICES_API_KEY, MICROSERVICES_TOKEN.
MCP server for microservices.sh: inspect verified Cloudflare-native modules/templates, generate app plans/projects, run checks, and trigger confirmation-gated preview deploys. Install via npx -y @microservices-sh/mcp.
List available microservices.sh app templates, including template ids and summaries. Use this before inspect_template, compose_app, generate_project, or run_checks when choosing a foundation for a new Cloudflare app.
inspect_template
Inspect one app template contract, including supported modules, default configuration, runtime metadata, and generation behavior. Use this before composing or generating a project from a specific template id.
list_modules
List available verified microservices.sh modules with ids, categories, summaries, versions, and maturity status. Use this to discover production building blocks before inspect_module, compose_app, or plan_add_module.
inspect_module
Inspect one module contract in detail, including permissions, hooks, events, resources, storage needs, and customization points. Use this before editing or adding a module so the agent understands the module boundaries.
list_module_docs
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Microservices Sh MCP is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, UI5 MCP Server belongs to Developer Tools using local stdio subprocess. Select Microservices Sh MCP when you need capabilities focused on developer tools and UI5 MCP Server when you require tools for developer tools.
List LLM-readable documentation pages available for module implementation guidance. Use this to discover local docs before get_module_doc or before changing generated source.
get_module_doc
Return an LLM-readable documentation page for a module, including rules, implementation notes, and agent guidance. Use this before coding against a module contract.
compose_app
Compose a template and selected modules into a checked app contract and lockfile plan without writing files. Use this to preview the exact app composition before generate_project or deployment planning.
validate_config
Validate a template, module list, and configuration object before generation or deployment. Use this to catch unsupported modules, missing settings, and invalid config before side effects.
generate_project
Generate project source files in memory for agent inspection. This tool does not write files; use it to review planned source, docs, migrations, and config before creating or editing a local project.
run_checks
Run local contract and readiness checks for a template/module composition. Use this before deployment planning to verify module compatibility, generated artifacts, and operational guardrails.
plan_add_module
Plan an approval-gated module addition against an optional existing microservices.lock.json. This tool reports intended lockfile changes and required review gates without writing files.
check_updates
Check locked module versions against the bundled registry snapshot. Use this to identify available module updates before plan_module_upgrade.
+5 more tools listed on main page
UI5 MCP Server Tools (10)
get_guidelines
This tool MUST be called once to retrieve UI5 guidelines before working on any UI5 (SAPUI5/OpenUI5) related task or project or creating a UI5 project. The guidelines provided by this tool MUST be followed to ensure best practices and avoid common pitfalls in UI5 development.
run_ui5_linter
Run UI5 linter on a UI5 project to find and optionally fix UI5 related problems like the usage of deprecated API. After making changes, you should always run the linter again to verify that no new problems have been introduced.
get_api_reference
Search the UI5 API reference for module names and symbols
get_project_info
Get general information about a local UI5 project.
create_ui5_app
Create a new basic SAPUI5 application implemented in TypeScript or JavaScript
get_version_info
Get version information for UI5 (OpenUI5 or SAPUI5)
get_integration_cards_guidelines
This tool MUST be called once to retrieve Integration Cards guidelines before working on any Integration Card related task or creating an Integration Card. The guidelines provided by this tool MUST be followed to ensure best practices and avoid common pitfalls in Integration Cards development.Integration Cards are also called 'UI Integration Cards' or 'UI5 Integration Cards'.
create_integration_card
Create a new Integration Card, UI Integration Card, or UI5 Integration Card
run_manifest_validation
Validates UI5 manifest file. After making changes, you should always run the validation again to verify that no new problems have been introduced.
get_typescript_conversion_guidelines
This tool MUST be called once before converting a UI5 (SAPUI5/OpenUI5) project from JavaScript to TypeScript. The instructions provided by this tool MUST be followed to ensure that the project setup and code is correctly converted.