OCI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oci-manageC | Manage Oracle Cloud Infrastructure resources including compute, storage, networking, databases, and monitoring. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'oci-manage' has a clear, distinct purpose covering multiple OCI resource types.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'oci-manage' follows a clear pattern (prefix_verb) that would be consistent if more tools existed.
A single tool for managing compute, storage, networking, databases, and monitoring in Oracle Cloud Infrastructure is too few for the apparent broad scope. This forces all operations through one interface, which is insufficient for proper agent interaction with such a complex domain.
The tool surface is severely incomplete for the stated purpose. A single 'manage' tool cannot provide the necessary CRUD/lifecycle operations for compute instances, storage volumes, network configurations, databases, and monitoring—this will cause significant agent failures due to missing specific actions.