feat: add JavaScript code server

[gebhardtr]

Description

Runs JavaScript in a sandbox to interact with OCI APIs.

TODO:

• utilize a proper parser like acorn

[mcp_servers.oci-javascript-mcp-server]
enabled = true
command = "node"
args = [
  "--no-node-snapshot",
  "--experimental-strip-types",
  "/path/to/mcp/src/oci-javascript-mcp-server",
]

[mcp_servers.oci-javascript-mcp-server.env]
OCI_CONFIG_PROFILE = "DEFAULT"

{
  "mcpServers": {
    "oci-javascript-mcp-server": {
      "type": "stdio",
      "command": "node",
      "args": [
        "--no-node-snapshot",
        "--experimental-strip-types",
          "/path/to/mcp/src/oci-javascript-mcp-server",
      ],
      "env": {
        "OCI_CONFIG_PROFILE": "DEFAULT"
      }
    }
  }
}

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

ok connected an upated mcp server, list my instances

Worked for 55s
The updated OCI MCP server found 14 instance resources:
bulletproof-tiger — Stopped
ol10-cheapest-20260521-2 — Stopped
...

when was the bulletproof vm created?

Worked for 11s
bulletproof-tiger was created on June 6, 2026 at 04:59:42 UTC (12:59:42 AM EDT).
...

can you figure out the current patch status?
Worked for 45s

I couldn’t verify a current patch level remotely.
bulletproof-tiger is not registered in OCI OS Management Hub, and it has no reported Compute Instance Agent plugins. Because it is also stopped, OCI cannot provide installed-package or pending-update data.
What is known:
Image: Oracle Linux 9.7
Image build: April 30, 2026
Current OS patch level: unknown
To verify it, the VM needs to be started and its instance agent/OS Management Hub registration repaired, then its available and installed updates can be queried.

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules