oracle-cloud-mcp
Related Servers
Alternatives to oracle-cloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Oracle Cloud Infrastructure (OCI) that exposes Compute, Networking, and Object Storage operations to MCP clients, with support for multiple authentication modes, read-only enforcement, and per-call region overrides.18MIT
- FlicenseNot gradedqualityBmaintenanceEnables interaction with Oracle Cloud Infrastructure through the MCP protocol. Supports dynamic profile selection and provides 85 tools for managing compute, databases, networking, IAM, storage, load balancers, OKE, monitoring, and cost management.-
- AlicenseNot gradedqualityCmaintenanceMCP server for Oracle Cloud Infrastructure Vault secrets, enabling secret retrieval, listing, creation, updates, deletion, and rotation with OCI authentication.1MIT
- AlicenseCqualityCmaintenanceAn MCP server that exposes Oracle Cloud Infrastructure (OCI) control plane to LLM clients, enabling management of compute, networking, storage, databases, and more through natural language.551Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Oracle Container Engine for Kubernetes (OKE) that enables inspection, querying, and troubleshooting of OKE clusters through safe, composable tools.Universal Permissive v1.0
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server exposing Oracle Cloud Infrastructure tools, resources and prompts.MIT
TDQS
Scored across 23 tools
Each tool is clearly scoped to a specific Oracle Cloud service and resource, with distinct actions. The service prefixes (compute, os, bv, vcn, adb, iam) prevent cross-service confusion, and within each service, tools like list, get, create, and start/stop are unambiguous.
Most tools follow the oci_<service>_<verb>_<noun> pattern (e.g., oci_compute_list_instances, oci_os_create_bucket). A few deviations exist, such as oci_vcn_list and oci_subnet_list omitting the resource noun, and oci_compute_instance_action using a different structure, but the overall pattern is readable and predictable.
With 23 tools spanning compute, storage, networking, database, and IAM, the count is reasonable for a cloud provider server. It covers multiple services without being excessively large, though it is slightly heavier than the ideal 3-15 range.
The set is heavily read-focused, providing list and get operations for most services, plus some actions like start/stop and bucket creation. However, it lacks core lifecycle operations such as compute instance creation/termination, object upload/download, and VCN deletion, leaving notable gaps for full management workflows.