
Mcp Oci
io.github.dockndevaiPublished by GitHub account dockndevaiv0.1.4Updated Oct 24, 2026
Oracle Cloud discovery + Terraform generation for AI agents — read-only, secret-safe.
Overview
An MCP server for Oracle Cloud Infrastructure that lets an assistant discover live OCI resources, map their dependencies, and generate Terraform, with secret-sh
- What you can do
- List compartments and regions, search resources, list everything in a compartment, and fetch a single resource's details from live OCI tenancy data. Generate Terraform HCL for known resource types such as VCNs, subnets, instances, buckets and compartments, or whole-compartment modules with provider variables. Build a dependency graph of nodes and edges with a suggested provisioning order. All payloads are redacted before being returned to the model.
- When to use it
- Useful when you want an assistant to explore an existing OCI tenancy, answer questions about what lives in a compartment, or produce starting-point Terraform and a provisioning order without hand-rebuilding infrastructure knowledge.
- Requirements
- Runs locally via npx (Node.js) as a stdio process. Needs a standard OCI config file at ~/.oci/config or instance principals, with the profile selected by OCI_PROFILE. Network access to OCI APIs. Optional variables OCI_MODE, OCI_COMPARTMENT_ALLOWLIST, OCI_REGION_ALLOWLIST, OCI_ALLOW_APPLY, OCI_DRY_RUN and OCI_AUDIT_LOG tune behaviour.
Installation
In SourceWeft
- Open Mcp Oci in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-oci
A Model Context Protocol server for Oracle Cloud Infrastructure (OCI). It gives an MCP-capable client (Claude Desktop, Claude Code, Cursor, Copilot, …) the ability to discover live OCI resources, map how they relate, and generate reproducible Terraform — with behaviour controlled entirely by flags.
Think of it as a Playwright-MCP for your cloud: instead of rebuilding infrastructure knowledge by hand, the model can ask "show all VCNs in the prod compartment" and "generate Terraform for this compartment" and get structured, secret-free answers.
Features
- Live discovery — compartments, regions, and any resource via OCI Resource Search.
- Terraform generation — faithful HCL for known types (VCN, subnet, instance, bucket, compartment) and annotated skeletons for the rest; whole-compartment modules with provider variables.
- Dependency graph — nodes/edges plus a suggested provisioning order (dependencies first).
- Secrets never reach the model — every payload is redacted before return.
- Security flags — access modes, compartment/region allowlists, provisioning gate, dry-run, and JSON audit logging (see below).
- Standard auth — OCI config file (
~/.oci/config) or instance principals. No credentials stored by the server.
Security model
Tools
Discovery (read): list_compartments, list_regions, search_resources, list_compartment_resources, get_resource
Terraform (read): generate_terraform, generate_compartment_terraform, build_dependency_graph
Quickstart — add to your agent
Published on npm as @dockndevai/mcp-oci. No clone or build needed — your MCP client runs it on demand with npx. Start in read-only mode; see .env.example for every variable and docs/CLIENTS.md for the full per-client guide.
Claude Code (CLI)
Claude Desktop · Cursor · Windsurf — same block in claude_desktop_config.json, .cursor/mcp.json, or ~/.codeium/windsurf/mcp_config.json:
OpenAI Codex CLI — in ~/.codex/config.toml:
VS Code (GitHub Copilot, Agent mode) — in .vscode/mcp.json:
Configure
Point it at a standard OCI config profile. For safety, use an IAM user/policy with
read-only (inspect/read) permissions on the compartments you want the agent to see.
Example prompts
- "List all compartments, then show every resource in the
prodcompartment." - "Generate Terraform for VCN
ocid1.vcn.oc1..…." - "Build a dependency graph for compartment
…and tell me the provisioning order."
Run from source (development)
Prefer the published package above. To run from a clone:
Develop
Roadmap
terraform plan/applyexecution behindread-write/admin+OCI_ALLOW_APPLY.- More resource-type mappers (load balancers, databases, DRGs, IAM policies).
- Cross-environment drift comparison.
Publishing
This server ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md for publishing to npm and listing on the MCP registry, Smithery, Glama, Cursor, and PulseMCP.
License
MIT
Source: README.md at commit 324c9e5
Tools
0Version history
1- v0.1.4LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
