ibmcloud-mcp-server
Related Servers
Alternatives to ibmcloud-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceComprehensive MCP server for managing all IBM Cloud services, offering 180+ tools across 16 domains to enable AI assistants to fully manage IBM Cloud infrastructure.1002-

Data Intelligence MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceProvides a modular MCP server to integrate with IBM Data Intelligence services, enabling secure interaction with data intelligence capabilities via tools and skills.19Apache 2.0- FlicenseNot gradedqualityDmaintenanceUnified MCP server for managing cloud resources across AWS, Google Cloud, Azure, and DigitalOcean by wrapping their CLI tools.-
- AlicenseAqualityCmaintenanceA minimal MCP server that exposes health-check and server information tools over stdio or HTTP, and can be containerized and deployed to IBM Code Engine.2Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for Oracle Cloud Infrastructure (OCI) that provides tools to manage Compute, Object Storage, Block Storage, Networking, Autonomous Database, and IAM via the official OCI SDK.2367 npmMIT
- FlicenseNot gradedqualityCmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.-
TDQS
Scored across 88 tools
Each tool follows a clear resource-action pattern with domain prefixes (cf, ks, cr, iam, resource, billing, catalog), making every tool's purpose distinct. Even similar operations like listing service instances in CF vs resource service instances are clearly separated by their prefixes and descriptions.
All tool names use the consistent ibmcloud_<domain>_<verb>_<noun> pattern, with plural nouns for list operations and singular for get/create/update/delete. Standalone commands like ibmcloud_login and ibmcloud_target fit the overall CLI convention without breaking the pattern.
At 88 tools, the server is far beyond a typical MCP size, even for a comprehensive cloud platform. While each tool is independently useful, the sheer number makes selection and discovery unwieldy, and the score guideline suggests 25+ is already too many.
The tool set covers most major IBM Cloud domains with reasonable CRUD coverage, but some lifecycle gaps exist. For example, access groups and their policies have create/list/get operations but no delete or update, and CF apps lack an explicit update op (though push serves that role). Overall, the core workflows are covered.