Repository containing reference implementations of MCP (Model Context Protocol) servers for managing and interacting with Oracle products. Each MCP server under src/
may be written in a different programming language, demonstrating MCP’s language-agnostic approach.
The Model Context Protocol (MCP) enables standardized, language-agnostic machine-to-machine workflows across data, models, and cloud resources. MCP servers implement specific tool suites, exposing them to MCP-compatible clients.
-
Proof-of-concept/Reference implementations:
This repository is not intended for production use; servers are provided as reference and for exploration, prototyping, and learning. -
Polyglot architecture:
Eachsrc/<server-name>/
directory represents a distinct MCP server, and these may use Python, Node.js, Java, or other languages.
- Supported OS: Linux, macOS, or Windows (varies by server; check server README)
- Git (for cloning this repository)
- Internet access (for downloading dependencies)
- Cloud access: Some servers require Oracle Cloud Infrastructure (OCI) credentials and configuration (OCI docs)
Note:
Each MCP server has its own specific requirements (e.g., language runtime version, libraries).
Always see the respective src/<server>/README.md
for detailed setup instructions.
Follow these instructions to get started as quickly as possible. Once finished, look here to set up your local development environment if you wish to contribute changes.
- Install
uv
from here - Install python with
uv python install 3.13
- If you are using OCI servers, configure your OCI authentication
- Add desired servers to your MCP client configuration
Below is an example MCP client configuration for a typical python server
(For Node.js/Java/other servers, follow respective instructions in that server’s README)
For macOS/Linux:
{
"mcpServers": {
"oracle-oci-api-mcp-server": {
"command": "uvx",
"args": [
"oracle.oci-api-mcp-server@latest"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
For OCI MCP servers, you'll need to install and authenticate using the OCI CLI.
- Install the OCI CLI
- Configure your OCI CLI profile
oci session authenticate --region=<region> --tenancy-name=<tenancy_name>
where:
<region>
is the region you would like to authenticate in (e.g. us-phoenix-1
)
<tenancy_name>
is the name of your OCI tenancy
Some MCP servers may not work with token-based authentication alone. See more about API key-based authentication here.
All actions are performed with the permissions of the configured OCI CLI profile. We advise least-privilege IAM setup, secure credential management, safe network practices, secure logging, and warn against exposing secrets.
Remember to refresh the session once it expires with:
oci session authenticate --profile-name <profile_name> --region <region> --auth security_token
<profile_name>
is the profile that you set up in the steps above. You can view a list of your profiles by running cat ~/.oci/config
on macOS/Linux if you forget which profile you have set up.
Each MCP server exposes endpoints that your client can connect to. To enable this connection, just add the relevant server to your MCP client’s configuration file. You can find the list of servers under the src
folder.
Refer to the sections below for client-specific configuration instructions.
Setup
Before continuing, make sure you have already followed the steps above in the Quick start section.
- If using Visual Studio Code, install the Cline VS Code Extension (or equivalent extension for your preferred IDE).
- Once installed, click the extension to open it.
- Click the MCP Servers button near the top of the the extension's panel.
- Select the Installed tab.
- Click Configure MCP Servers to open the
cline_mcp_settings.json
file. - In the
cline_mcp_settings.json
file, add your desired MCP servers in themcpServers
object. Below is an example for for the generic OCI API MCP server. Make sure to save the file after editing.<profile_name>
is the profile that you set up during the authentication steps.
For macOS/Linux:
{
"mcpServers": {
"oracle-oci-api-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"oracle.oci-api-mcp-server@latest"
],
"env": {
"OCI_CONFIG_PROFILE": "<profile_name>",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
For Windows - TODO
- Once installed, you should see a list of your MCP Servers under the Installed tab. They will have a green toggle that shows that they are enabled.
- Click Done when finished.
Setup
Before continuing, make sure you have already followed the steps above in the Quick start section.
- You can place MCP configurations in two locations, depending on your use case:
Project Configuration: For tools specific to a project, create a .cursor/mcp.json
file in your project directory. This allows you to define MCP servers that are only available within that specific project.
Global Configuration: For tools that you want to use across all projects, create a ~/.cursor/mcp.json
file in your home directory. This makes MCP servers available in all your Cursor workspaces.
.cursor/mcp.json
For macOS/Linux:
{
"mcpServers": {
"oracle-oci-api-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"oracle.oci-api-mcp-server"
],
"env": {
"OCI_CONFIG_PROFILE": "<profile_name>",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
<profile_name>
is the profile that you set up during the authentication steps.
For Windows - TODO
- In your Cursor Settings, check your Installed Servers under the MCP tab to ensure that your
.cursor/mcp.json
was properly configured.
Setup
Before continuing, make sure you have already followed the steps above in the Quick start section.
- Download Ollama
- Start the Ollama server
For macOS: If installed via the official installer, ollama start
. If installed via homebrew, brew services start ollama
For Windows: If installed via the official installer, the server is typically configured to start automatically in the background and on system boot.
For Linux: sudo systemctl start ollama
- Verify the ollama server has started with
curl http://localhost:11434
. A successful response will typically be "Ollama is running". - Fetch the large language model, where
<model>
is the name of your desired model (e.g.qwen2.5
), withollama pull <model>
. For more options, check Ollama's list of models that support tool calling. - Install
go
from here - Install
mcphost
withgo install github.com/mark3labs/mcphost@latest
- Add go's bin to your PATH with
export PATH=$PATH:~/go/bin
- Create an mcphost configuration file (e.g.
./mcphost.json
) - Add your desired server to the
mcpServers
object. Below is an example for for the compute OCI MCP server. Make sure to save the file after editing.
For macOS/Linux:
{
"mcpServers": {
"oracle-oci-api-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"oracle.oci-api-mcp-server"
],
"env": {
"OCI_CONFIG_PROFILE": "<profile_name>",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
<profile_name>
is the profile that you set up during the authentication steps.
For Windows - TODO
- Start
mcphost
withOCI_CONFIG_PROFILE=<profile> mcphost -m ollama:<model> --config <config-path>
<model>
is the model you chose above<profile>
is the name of the OCI CLI profile that you set up above<config-path>
is the path to the mcphost configuration json file that you made above
This section will help you set up your environment to prepare it for local development if you wish to contribute changes.
-
Set up python virtual environment and install dev requirements
python3 -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate pip install -r requirements-dev.txt
-
Locally build and install servers within the virtual environment
make build make install
-
Add desired servers to your MCP client configuration, but run them using the locally installed server package instead
Below is an example MCP client configuration for a typical python server using the local server package
(For Node.js/Java/other servers, follow respective instructions in that server’s README)
For macOS/Linux:
{
"mcpServers": {
"oracle-oci-api-mcp-server": {
"command": "uv",
"args": [
"run"
"oracle.oci-api-mcp-server"
],
"env": {
"VIRTUAL_ENV": "<path to your cloned repo>/mcp/venv",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
where <path to your cloned repo>
is the absolute path to wherever you cloned this repo that will help point to the venv created above (e.g. /Users/myuser/dev/mcp/venv
)
.
├── src/
│ ├── dbtools-mcp-server/ # MCP server (Python example)
│ ├── another-mcp-server/ # (Possible Node.js, Java, or other implementation)
│ └── ...
├── LICENSE.txt
├── README.md
├── CONTRIBUTING.md
└── SECURITY.md
Each server subdirectory includes its own README.md
with language/runtime details, installation, and usage.
You can modify the settings of your MCP client to run your local server. Open your client json settings file and update it as needed. For instance:
{
"mcpServers": {
"oracle-oci-api-mcp-server": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"oracle.oci-api-mcp-server"
],
"env": {
"VIRTUAL_ENV": "<path to your cloned repo>/oci-mcp/.venv",
"FASTMCP_LOG_LEVEL": "ERROR"
}
}
}
}
where <absolute path to your server code>
is the absolute path to the server code, for instance
/Users/myuser/dev/oci-mcp/src/oci-identity-mcp-server/oracle/oci_identity_mcp_server
.
The Model Context Protocol (MCP) provides Inspector which is a developer tool for testing and debugging MCP servers. More information on Inspector can be found in the documentation.
The Inspector runs directly through npx without requiring installation. For instance, to inspect your locally developed server, you can run:
npx @modelcontextprotocol/inspector \
uv \
--directory <absolute path to your server code> \
run \
server.py
Inspector will run your server on localhost (for instance: http://127.0.0.1:6274) which should automatically open the tool for debugging and development.
This project welcomes contributions from the community. Before submitting a pull request, please review our contribution guide.
Please consult the security guide for our responsible security vulnerability disclosure process.
Copyright (c) 2025 Oracle and/or its affiliates.
Released under the Universal Permissive License v1.0 as shown at
https://oss.oracle.com/licenses/upl/.
Developers choosing to distribute a binary implementation of this project are responsible for obtaining and providing all required licenses and copyright notices for the third-party code used in order to ensure compliance with their respective open source licenses.
Users are responsible for their local environment and credential safety. Different language model selections may yield different results and performance.