Official Oracle repository of MCP reference servers for OCI CLI, OCI SDK, Oracle Database services, Cloud Guard, Object Storage, Monitoring, Logging, and Oracle Database documentation workflows.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
6 prerequisites to line up before setup. Includes a review or approval gate.
Safety & privacy surface
6 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access.
{
"mcpServers": {
"oracle-oci-api": {
"type": "stdio",
"command": "uvx",
"args": ["oracle.oci-api-mcp-server@latest"],
"env": {
"OCI_CONFIG_PROFILE": "<least-privilege-profile>",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}Oracle MCP Servers is Oracle's official repository of Model Context Protocol
reference servers for Oracle products and OCI workflows. The repository contains
multiple server implementations under src/, including OCI API, OCI Cloud,
OCI Database, Cloud Guard, Compute, Object Storage, Logging, Monitoring, Usage,
Support, and Oracle Database documentation servers.
Oracle describes the repository as proof-of-concept and reference implementations for exploration, prototyping, and learning. Treat these servers as powerful cloud and database control surfaces, and review each server-specific README before enabling it in a Claude workflow.
These sources were reviewed on 2026-06-06. Prefer the live repository, top-level README, server-specific READMEs, best-practices guide, and license for current server availability, package names, transport modes, authentication requirements, and safety guidance.
src/ for OCI and Oracle product workflows.oracle.oci-api-mcp-server for OCI CLI command help and command execution.oracle.oci-cloud-mcp-server for OCI SDK client discovery, operation description, and operation invocation.Start with the narrowest server for the task. For OCI CLI-backed workflows, the
top-level README shows oracle.oci-api-mcp-server over stdio:
{
"mcpServers": {
"oracle-oci-api": {
"type": "stdio",
"command": "uvx",
"args": ["oracle.oci-api-mcp-server@latest"],
"env": {
"OCI_CONFIG_PROFILE": "<least-privilege-profile>",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
Use a dedicated OCI profile with only the permissions required for the workflow.
For other servers, follow the server-specific README under src/.
Oracle MCP Servers can put Claude close to real cloud infrastructure. Use read-only or narrowly scoped IAM policies where possible, require human review for create, update, delete, ticket, support, billing, or resource-changing operations, and keep high-impact servers disabled until the exact workflow is approved.
Do not paste OCI private keys, security tokens, client secrets, tenancy details, or raw configuration files into prompts or issues. Review logs and model transcripts for OCIDs, compartment names, database resource details, object names, support metadata, billing data, and other cloud inventory before sharing.
Oracle offers commercial cloud, database, and support services. This listing is not sponsored, paid, or affiliate-driven, and it is scoped to the source-backed open Oracle MCP repository.
No dedicated Oracle MCP Servers, oracle/mcp, OCI MCP, or Oracle Database MCP
entry was found in content/mcp, content/tools, content/guides,
content/agents, or content/skills.
Show that Oracle MCP Servers is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/oracle-mcp-servers)Oracle MCP Servers side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
| Field | Official Oracle repository of MCP reference servers for OCI CLI, OCI SDK, Oracle Database services, Cloud Guard, Object Storage, Monitoring, Logging, and Oracle Database documentation workflows. Open dossier | Comprehensive AWS cloud services integration for infrastructure management, deployment, and monitoring Open dossier | Official Microsoft Azure MCP server that connects Claude and other MCP clients to Azure subscriptions, resource groups, storage, databases, Key Vault, Monitor, App Service, AKS, AI Search, Cosmos DB, RBAC, pricing, and other Azure services through local stdio or self-hosted HTTP transports. Open dossier | Connect Claude to DigitalOcean — manage Apps, Droplets, managed Databases, Kubernetes, Container Registry, networking, and Functions — with DigitalOcean's official Model Context Protocol server. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trustDiffers | Package not verified | Package verified | Package not verified | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | Source-backed | Source-backed |
| SubmitterDiffers | oktofeesh1 | — | oktofeesh1 | — |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand |  AWS | |||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | First-party | Source-backed | Source-backed |
| Author | Oracle | AWS Labs | Microsoft | DigitalOcean |
| Added | 2026-06-06 | 2025-09-16 | 2026-06-04 | 2026-06-17 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Oracle describes this repository as proof-of-concept and reference implementations for exploration, prototyping, and learning rather than production use. The OCI API MCP server can run OCI CLI commands using the configured OCI CLI profile. The OCI Cloud MCP server can discover and invoke OCI Python SDK client operations, including operations that may create, update, delete, or expose cloud resources. Service-specific servers cover high-impact areas such as Compute, Database, Identity, Object Storage, Networking, Load Balancer, Monitoring, Logging, Usage, Support, and Cloud Guard. All cloud actions run with the permissions granted to the OCI profile or authenticated OCI IAM user, so use dedicated least-privilege credentials and human review for write operations. HTTP-capable servers require OAuth/IAM setup, confidential client secrets, restricted host binding, and careful redirect URI configuration before non-local use. | ✓Scope AWS credentials to the intended accounts, regions, and services because infrastructure actions can affect production resources. | ✓Start in read-only mode and narrow the exposed namespaces or individual tools before enabling broader Azure access. Microsoft documents read-only mode, namespace filters, single-tool mode, and learn mode as controls for reducing the active MCP surface. Azure MCP tools can inspect and manage real cloud resources. Depending on the tool and RBAC role, actions can create, update, delete, deploy, restart, query, or reconfigure resources and can incur cloud spend. Keep human approval on destructive, cost-bearing, deployment, RBAC, Key Vault, database, storage, messaging, and production-environment actions. Do not disable user confirmation for high-risk or sensitive-data commands unless the automation environment is tightly controlled. The server authenticates with Azure credentials available to the local machine or hosted environment. Limit the credential chain with `AZURE_TOKEN_CREDENTIALS`, managed identities, service principals, and least-privilege Azure RBAC where practical. For self-hosted HTTP deployments, configure Entra ID inbound authentication, outbound authentication strategy, network exposure, logging, and per-user versus server-identity audit requirements before sharing the endpoint. Docker setup uses Azure credential environment variables such as `AZURE_TENANT_ID`, `AZURE_CLIENT_ID`, and `AZURE_CLIENT_SECRET`; protect those values and never commit the env file. Microsoft documents telemetry environment variables for the server. Review `AZURE_MCP_COLLECT_TELEMETRY` and `AZURE_MCP_COLLECT_TELEMETRY_MICROSOFT` before using the server in sensitive environments. This is the Azure services MCP server. It is distinct from the Azure DevOps MCP server, which focuses on work items, repositories, pull requests, pipelines, wikis, and test plans. | ✓Tools can create, update, restart, and delete live infrastructure (Apps, Droplets, Databases) — scope the API token and select only the --services you need. Destructive actions (delete, rollback) act on production resources; confirm before running them through Claude. |
| Privacy notes | ✓OCI profiles, OCIDs, compartment names, tenancy details, resource names, API parameters, command text, responses, logs, and errors can reveal sensitive cloud infrastructure details. OCI actions may expose customer data, backups, logs, object names, support metadata, database resource state, IAM configuration, or billing and usage information. IDCS client IDs, client secrets, OCI config files, private keys, security tokens, region names, and profile names should stay out of prompts, issues, logs, screenshots, and committed files. Oracle Database Documentation MCP builds and stores a local documentation index, so review index location, update cadence, and log retention. | ✓AWS resource names, configuration, metrics, logs, ARNs, and account metadata may be exposed through tool calls and responses. | ✓Tool results can expose tenant IDs, subscription IDs, resource groups, resource names, tags, deployment outputs, Azure Monitor logs, metrics, pricing data, quotas, RBAC assignments, policy data, app settings, database metadata, storage account and blob metadata, and service-specific configuration. Key Vault, App Configuration, Storage, database, Service Bus, Event Hubs, Communication Services, and deployment tools may expose secrets, connection strings, keys, certificates, message contents, sample records, or customer data when the authenticated identity has permission. Microsoft documents user confirmation for tools that handle sensitive data, including Key Vault secrets, connection strings, passwords, certificate private keys, and other confidential values. Treat those prompts as a required guardrail rather than friction. MCP client logs, AI transcripts, local terminal history, hosted server logs, prompt traces, generated runbooks, and downstream tickets can retain Azure resource inventory and returned data outside Azure's original access and retention boundaries. Remote HTTP deployments require Entra ID bearer tokens on inbound requests and a configured outbound Azure authentication strategy. Choose On-Behalf-Of when per-user RBAC and audit trails matter, and managed identity only when the shared-server identity model is acceptable. Read-only mode reduces mutation risk, but it does not make returned Azure metadata or data safe to share with untrusted models, logs, chats, or third-party tools. | ✓Resource metadata, logs, and metrics enter the MCP client context and the model's prompt. The DIGITALOCEAN_API_TOKEN is a secret — store it in the client config or environment, never in shared repositories. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Comprehensive AWS cloud services integration for infrastructure management, deployment, and monitoring
Connect Claude to Azure subscriptions, resource groups, services, logs, storage, databases, Key Vault, RBAC, pricing, and deployment context.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.