OCI CLI MCP server
Listed on its own since 2026-09-25. Until then it was part of oracle-data-studio-mcp-server, where its earlier checks remain.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"oracle-oci-api-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# OCI API MCP Server ## Overview This server provides tools to run OCI CLI commands to interact with the OCI services. It includes tools to help with OCI command execution and provide helpful information. ## Running the server ### STDIO transport mode ```sh uvx oracle.oci-api-mcp-server ``` ### HTTP streaming transport mode `oracle.oci-api-mcp-server` supports `stdio` only. ## Tools | Tool Name | Description | | --- | --- | | get_oci_command_help | Returns helpful instructions for running an OCI CLI command. Only provide the command after 'oci', do not include the string 'oci' in your command. | | run_oci_command | Runs an OCI CLI command. This tool allows you to run OCI CLI commands on the user's behalf. Only provide the command after 'oci', do not include the string 'oci' in your command. | | get_oci_commands (Resource) | Returns helpful information on various OCI services and related commands. | ⚠️ **NOTE**: All actions use the configured OCI CLI profile. `OCI_CLI_AUTH` is authoritative: when it is set, `run_oci_command` adds no authentication override and lets the OCI CLI select authentication. Otherwise, `run_oci_command` resolves `OCI_MCP_AUTH_TYPE` using `oracle-mcp-common`. Supported values are `api_key`, `security_token`, `instance_principal`, `resource_principal`, and `oke_workload_identity`. `auto` selects API-key or session-token authentication from the selected profile's direct configuration. The server rejects unclassifiable `auto` profiles and auth modes without OCI CLI equivalents (`identity_domain_upst`, `instance_principal_delegation`, and `resource_principal_delegation`). The server owns OCI CLI authentication and connection configuration. Commands cannot supply global overrides such as `--auth`, `--profile`, `--config-file`, `--endpoint`, or `--proxy`. The server also uses an empty OCI CLI RC file, so command and parameter aliases, canned queries, defaults, and settings from a user CLI RC file are not applied. Use least-privilege IAM …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.