Shared utilities for Oracle MCP Python servers
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-mcp-common","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.
# Oracle MCP Common `oracle-mcp-common` is the shared Python library for Oracle MCP servers. It provides reusable components that belong in more than one server while keeping server-specific tools, client lifecycles, and service behavior in each server. The library currently provides OCI SDK authentication through `oracle_mcp_common.auth`. Future shared modules should follow the same server-agnostic approach and expose a focused, documented public API. ## Package requirements - Python 3.13 or later - OCI Python SDK 2.179.0 or later - FastMCP 3.4.5 or later in the 3.x series for the optional HTTP IDCS authentication API An adopting server normally declares a bounded dependency on this package: ```toml dependencies = [ "oracle-mcp-common>=0.2.0,<0.3.0", ] ``` ## Authentication module `oracle_mcp_common.auth` resolves outbound authentication for OCI Python SDK clients. It chooses a supported authentication type and returns the SDK-native ingredients needed to create a service client. The module owns credential resolution only. Each server continues to own its OCI client type, retry and circuit-breaker policy, `additional_user_agent`, and client lifecycle. ### Quick start Set up OCI credentials for the authentication type you intend to use, then build a context and pass its config and signer to the OCI SDK client. ```python import oci from oracle_mcp_common import build_auth_context auth_context = build_auth_context() config = { **auth_context.config, "additional_user_agent": "oci-example-mcp/1.2.3", } client = oci.object_storage.ObjectStorageClient(config, signer=auth_context.signer) ``` The returned `AuthContext` contains: | Field | Meaning | | --- | --- | | `auth_type` | The selected `AuthType`; `auto` is resolved to `api_key` or `security_token`. | | `config` | An OCI SDK config dictionary. It contains the resolved `region` when one is available. | | `signer` | The OCI SDK signer to pass to a client constructor. | | `tenancy_id` | Tenancy …
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.