APAM OS MCP Gateway

Published package name:

• @apam-ai/v10-mcp

What it provides:

• an npx-friendly MCP server entrypoint
• a bridge from MCP-aware clients into APAM OS governance endpoints
• a small, published adapter surface that stays separate from the Python core

Local development:

npm --prefix sdk/typescript/mcp run build
npm --prefix sdk/typescript/mcp run check

Local execution:

npx --yes --package ./sdk/typescript/mcp v10-mcp --help
npx --yes --package ./sdk/typescript/mcp v10-mcp --mode interactive
npx --yes --package @apam-ai/v10-mcp v10-mcp --help

Publish path:

npm login
cd sdk/typescript/mcp
npm publish --access public

GitHub Actions note:

• This package is intended to publish from the public repo: https://github.com/Apam-AI/apam-os.git.
• Keep sdk/typescript/mcp/package.json repository.url aligned with that repo so npm provenance and source links point at the correct origin.
• Preferred CI path is GitHub Actions trusted publishing rather than a long-lived local token.
• Recommended workflow shape:
  • trigger on version tags or manual dispatch
  • permissions: contents: read, id-token: write
  • run npm --prefix sdk/typescript/mcp ci
  • run npm --prefix sdk/typescript/mcp run check
  • run npm --prefix sdk/typescript/mcp run build
  • publish with npm publish --provenance --access public
• If trusted publishing is not enabled yet, use a short-lived npm automation token in Actions secrets and replace it later with trusted publishing.
• Before each publish, bump the package version. npm will reject republising the same version.

The gateway is intentionally thin. It should remain an adapter around the kernel, not a second kernel implementation.