server

Server

Getting started

Create IAM Domain

IAM Domain Configuration

Follow Steps from IAM Domain Configuration document.

Prepare server

1. Install uv
2. Set environment variables:

export IDCS_CLIENT_ID=<value>
export IDCS_CLIENT_SECRET=<value>
# this isn't a URL 👇
export IDCS_DOMAIN="hostname:port from IDCS Domain URL"

2. Start the server

uv run server.py

3. Optional: set token (JWT retrieved from IDCS Oauth/OIDC); copy it to clipboard and then:

export TOKEN=$(pbpaste)

4. Clear contents of clipboard (copy something else)
5. Run client

uv run client.py

Architecture

The following diagram illustrates the architecture of the MCP Server:

sequenceDiagram
    box User Tenancy
        participant Client
    end
    box Service Tenancy
        participant MCP Server
        participant IDCS
    end
    box OCI
        participant OCI APIs
    end

    Client->>MCP Server: Authentication Request
    MCP Server->>IDCS: Redirect to IDCS Authentication
    Client->>IDCS: Authenticate
    IDCS->>Client: Authorization Token
    Client->>MCP Server: Request with Authorization Token
    MCP Server->>IDCS: Validate Token
    IDCS->>MCP Server: Token Validation Response
    MCP Server->>IDCS: Exchange Token for UPST
    IDCS->>MCP Server: UPST
    MCP Server->>OCI APIs: Request with UPST (Token Exchange Signer)
    OCI APIs->>MCP Server: Response
    MCP Server->>Client: Response

Loading

License

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/.

Third-Party APIs

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.

Disclaimer

Users are responsible for their local environment and credential safety. Different language model selections may yield different results and performance.

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.