Mcp Server For Oracle Cloud Infrastructure (oci)

Created By
jopsis8 months ago
Overview

What is MCP Server for Oracle Cloud Infrastructure (OCI)?

MCP Server for OCI is a server implementation of the Model Context Protocol (MCP) that allows large language models (LLMs) like Claude to interact directly with Oracle Cloud Infrastructure resources.

How to use MCP Server for OCI?

To use the MCP Server, clone the repository, install the required dependencies, and start the server using Python. You can choose to start it with a default profile or select a profile dynamically at runtime.

Key features of MCP Server for OCI?

  • Dynamic profile selection for OCI tenancies without server restart.
  • Connection to Oracle Cloud using standard OCI CLI configuration.
  • 85 comprehensive tools for managing OCI resources across 11+ service categories.
  • Instance lifecycle management (start, stop) and database management.
  • Integration with the MCP protocol for seamless access from LLMs.

Use cases of MCP Server for OCI?

  1. Managing OCI resources through a command-line interface.
  2. Facilitating LLM interactions with cloud resources for enhanced AI capabilities.
  3. Automating cloud resource management tasks.

FAQ from MCP Server for OCI?

  • What are the prerequisites for using MCP Server?

    You need Python 3.10 or higher, OCI CLI configured, and appropriate permissions in Oracle Cloud.

  • Is there a graphical interface for MCP Server?

    No, MCP Server is primarily command-line based for managing OCI resources.

  • Can I switch between different OCI profiles?

    Yes, you can switch profiles dynamically without restarting the server.

Server Config

{
  "mcpServers": {
    "mcp-server-oci": {
      "command": "python",
      "args": [
        "-m",
        "mcp_server_oci.mcp_server",
        "--profile",
        "DEFAULT"
      ],
      "env": {
        "PYTHONPATH": "/<PATH_TO_MCP>/mcp-server-oci",
        "FASTMCP_LOG_LEVEL": "INFO"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
7 months ago
Author Name
jopsis
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago