About oac-mcp-connect (Preview)

Oracle Analytics Cloud can provide an oac-mcp-connect utility from the user's profile when developer options are enabled. The utility is a local stdio bridge for Oracle Analytics Cloud MCP servers and can handle browser-based or token-file authentication on behalf of the MCP client.

Use oac-mcp-connect when:

• You want to connect OAC MCP tools to desktop MCP clients such as Claude Desktop.
• You're using a client that doesn't directly manage MCP HTTP session initialization and Mcp-Session-Id headers.

The built bundle runs with Node.js 18 or newer. The detailed README is in the downloaded utility bundle.

High-Level Codex Configuration Shape

[mcp_servers.oac]
enabled = true
command = "node"
args = [
  "/absolute/path/to/oac-mcp-connect.js",
  "https://my-oac.example.com",
  "--sync"
]

High-Level Claude Desktop Configuration Shape

{
  "mcpServers": {
    "oac": {
      "command": "node",
      "args": [
        "/absolute/path/to/oac-mcp-connect.js",
        "https://my-oac.example.com",
        "--sync"
      ]
    }
  }
}

For browser authentication, omit --headless and omit token-file arguments; the connector can open a browser when it needs a new login. For headless or non-interactive runs, use a token file downloaded from the OAC profile and pass it before --headless:

[mcp_servers.oac_token]
enabled = true
command = "node"
args = [
  "/absolute/path/to/oac-mcp-connect.js",
  "https://my-oac.example.com",
  "/absolute/path/to/token.json",
  "--headless",
  "--sync"
]

The connector can also read a JSON config file for multiple OAC environments. Use the README in the utility bundle for the full set of options, including token paths, browser/headless mode, logging, custom headers, tool filters, and experimental/deprecated tool flags.