Recipe
mcp-stdio-bridge
A Model Context Protocol server published as an npm or PyPI package that speaks only stdio, run on Kubernetes behind supergateway 4.1.0, which serves it over Streamable HTTP. The helm provider synthesizes a Deployment running the bridge image, pinned by digest, for the runtime infra.stdio_runtime names, and a ClusterIP Service on infra.port. The bridge starts the command line infra.stdio_command names, with each item quoted so it reaches the server as written; the launcher fetches the package when the server starts, so the cluster reaches the package registry then. One server process runs per client session, at the path /mcp, and the bridge's /healthz endpoint is the readiness probe. provides.endpoint is the Service's address with that path. Variables the server reads its credentials from arrive through the server_env slot: every data key of the Secret its attachment names becomes one variable in the bridge's environment, by reference, and the server inherits that environment. An edge from the tool, on a socket the author names, delivers the names its `inject:` block dictates into that environment too, or as files from a ConfigMap emitted beside the Deployment. Reach for this realization where the server is a package speaking stdio; reach for helm/mcp where it ships as an image serving HTTP, for helm/mcp-remote where someone else already runs it, and for compose/mcp-stdio-bridge under Docker Compose. infra.image, infra.endpoint and the component's own `inject:` block are refused here. What it renders is checked by building it; the bridge's behaviour is read from its documentation and source at the pinned release, and no run of this realization has been observed.
版本
来源
- 内容摘要
- sha256:0865babb558f2ee6446bafbd0eb177cd0b46a30a9793968eaa1260afae2a7cbe
- 发布时间
- 2026-11-10T10:25:27Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:fbd08ad949c67f9c497aca393277e2b7dc3e5ae3b09ace4af6603b7a60f093a9
此版本的引用
oci://hub.aggrega.ai/recipe/helm/mcp-stdio-bridge:1.0.0- 目标
- —
- 实现
- core/ai-tool/mcp:1.0.0
提供
此配方为使用方接入的确定性指针模板。
| 名称 | 模板 |
|---|---|
| host | {{ .context.rendered_name }}-default |
| port | {{ .infra.port }} |
| endpoint | http://{{ .context.rendered_name }}-default:{{ .infra.port }}{{ .locals.path }} |
| protocol | http |
| credential_header |
Workload
Workload · form: stateless · containers: main
局部变量
| 名称 | 模板 |
|---|---|
| npm_image | ghcr.io/supercorp-ai/supergateway:4.1.0@sha256:1938c43538a5308bce07d58028e9de00b7acfecb40b39b059b2f3931800ad910 |
| pypi_image | ghcr.io/supercorp-ai/supergateway:4.1.0-uvx@sha256:660c97d4ee58498f4654e1dc60682f4f4ccab363025c9b8b415d04b4e823025e |
| path | /mcp |
| health_path | /healthz |
值映射
未声明值映射。
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 实现实现契约兼容
core/ai-tool/mcp:1.0.0
所有必需输出均已满足,且提供的每个输出都在契约中列出。
被使用
目录中没有任何内容依赖此实体。