Public Wrapper Around Non-Public Runtime
Some packages are intentionally public as installers or access layers while the full runtime remains outside the visible package surface.
Package
palantir-mcp
A public wrapper package that sets up access to a broader MCP runtime rather than implementing that runtime itself.
- Public package explicitly positions itself as a wrapper/installer layer.
- Handles setup, preflight checks, and process launch behavior.
- Cleaner seam than Maker because the boundary is documented instead of hidden.
- Strong evidence of Palantir publishing access tooling separately from the full runtime.
- Public wrapper launches a broader MCP runtime through a separate access layer.
Relevant code
Most revealing source snippet
published: dist/index.js
src/spawn.ts
open source file ->// generalized snippet; identifiers intentionally redacted
const child = spawn('npx', ['-y', 'runtime-package', ...args], {
stdio: 'inherit',
env: {
...process.env,
PACKAGE_REGISTRY: registryUrl,
ACCESS_TOKEN: accessToken,
},
})Notes
Why it matters
This package is useful as a contrast case.
Unlike the Maker seam, where the boundary shows up inside a function-discovery path, palantir-mcp describes its own boundary clearly. Its public source is focused on preflight checks and process launch behavior rather than implementing the full MCP runtime directly.
That makes it a good example of a public wrapper around a broader runtime surface: the public package is useful on its own, while the full runtime remains outside the main package implementation.
Seams