Oracle Cloud
Give your agent Oracle Cloud Infrastructure CLI access so tenancy changes and inspections stay inside the coding workflow.
Overview
Oracle Cloud Infrastructure MCP is an Operate-phase MCP server that lets coding agents run OCI CLI workflows from the editor via stdio.
What is this MCP server?
- Oracle Cloud Infrastructure MCP via npm oracle-cloud-mcp v1.0.1
- Stdio MCP for agent-driven OCI CLI workflows
- GitHub: ExpertVagabond/oracle-cloud-mcp
- Supports solo builders on OCI free tier or paid tenancy who automate with agents
- Server version 1.0.1
- npm package: oracle-cloud-mcp
- Transport: stdio
What problem does it solve?
Operating on OCI with an AI agent fails when every compartment check or resource change forces a separate oci CLI terminal session.
Who is it for?
Solo builders with active OCI tenancy who want agent-assisted infrastructure commands and repeatable ops playbooks.
Skip if: Teams all-in on GCP or Azure with no Oracle footprint, or beginners who need a cloud picker before any CLI bridge.
What do I get? / Deliverables
After oracle-cloud-mcp is registered, your agent can execute documented OCI CLI operations in-context while you ship and run infra.
- Stdio MCP server configuration for oracle-cloud-mcp
- Agent tools backed by OCI CLI command patterns
- In-editor Oracle Cloud operations for small-team ops loops
Recommended MCP Servers
Journey fit
How it compares
OCI MCP is an infrastructure CLI integration, not an Oracle architecture certification path or Terraform replacement.
Common Questions / FAQ
Who is Oracle Cloud Infrastructure MCP for?
It is for developers on OCI using Claude Code, Cursor, or Codex who want oci CLI operations available as MCP tools.
When should I use Oracle Cloud Infrastructure MCP?
Use it when you operate or extend Oracle Cloud resources and want the agent to run CLI workflows during deploy fixes and infra upkeep.
How do I add Oracle Cloud Infrastructure MCP to my agent?
Install oracle-cloud-mcp from npm, add a stdio MCP server block in your agent config, configure OCI CLI credentials, then restart.