oracle.oci-cloud-mcp-server

# OCI Cloud MCP Server ## Overview This server is a thin wrapper over the official OCI Python SDK (no OCI CLI subprocess calls). Think in SDK terms: `client class -> method -> kwargs`. Discovery is SDK-first, with thin keyword/resource-action fallback search when you genuinely cannot infer the client or method. It exposes generic tools that let you: - List OCI SDK clients available in the current environment - Search for the right OCI client operation by short keyword/resource-action search - Inspect the exact contract of an SDK method before calling it - Invoke any OCI SDK client operation by fully-qualified client class and method name - Discover available operations for a given OCI client Recommended low-token workflow: 1. If you already know the SDK client class and method, call `describe_oci_operation` or `invoke_oci_api` directly. 2. If the service family is already obvious, call `list_client_operations` on that client class first. 3. Otherwise, call `find_oci_api` only as a thin escape-hatch fallback with a short SDK-oriented resource/action query like `"list regions"` or `"create vcn"` rather than a full sentence. Keep `limit` small (`3-5`) on the first discovery call. 4. Call `describe_oci_operation` for the chosen `client_fqn` + `operation` when you need parameter details. 5. Call `invoke_oci_api`. Its default `result_mode="auto"` keeps list, summarize, and paginated results compact. Use `result_mode="full"` only when you need the full payload, and prefer `fields` when you only need a few exact top-level values. 6. Call `list_oci_clients` only for capability discovery/debugging, or when search is ambiguous. ## Architecture ```mermaid flowchart TD A["LLM / Agent"] -->|Known client + method| B["describe_oci_operation / invoke_oci_api"] A -->|Known client family| C["list_client_operations"] A -->|Only if unclear| D["find_oci_api"] C --> B D --> B B --> E["OCI Cloud MCP Server"] E --> F["OCI Python SDK clients"] F --> G["…