orca-mcp 0.3.6

orca-mcp 0.3.6

Bridge version stays coupled to the npm package version (0.3.6).

Install

# stdio (local MCP hosts) — pin the version
npx -y orca-mcp@0.3.6 --stdio

# container (preferred for privileged/long-lived hosts)
docker run --rm -i \
  -e ORCA_BRIDGE_TOKEN="$ORCA_BRIDGE_TOKEN" \
  ghcr.io/buildcontext/orca-mcp:0.3.6 --stdio

Artifacts

• npm: https://www.npmjs.com/package/orca-mcp/v/0.3.6
• GHCR: ghcr.io/buildcontext/orca-mcp:0.3.6
• MCP Registry name: io.github.buildcontext/orca-mcp

Notes

• Published to npm with provenance (npm publish --provenance).
• Image runs as non-root UID 1001; no secrets baked in.
• Read SECURITY.md before exposing the bridge.

orca-mcp 0.3.0

orca-mcp 0.3.0

Bridge version stays coupled to the npm package version (0.3.0).

Install

# stdio (local MCP hosts) — pin the version
npx -y orca-mcp@0.3.0 --stdio

# container (preferred for privileged/long-lived hosts)
docker run --rm -i \
  -e ORCA_BRIDGE_TOKEN="$ORCA_BRIDGE_TOKEN" \
  ghcr.io/buildcontext/orca-mcp:0.3.0 --stdio

Artifacts

• npm: https://www.npmjs.com/package/orca-mcp/v/0.3.0
• GHCR: ghcr.io/buildcontext/orca-mcp:0.3.0
• MCP Registry name: io.github.buildcontext/orca-mcp

Notes

• Published to npm with provenance (npm publish --provenance).
• Image runs as non-root UID 1001; no secrets baked in.
• Read SECURITY.md before exposing the bridge.