Recipe
mcp-stdio-bridge
A Model Context Protocol server published as an npm or PyPI package that speaks only stdio, run for local development via Docker Compose behind supergateway 4.1.0, which serves it over Streamable HTTP. The compose provider synthesizes one service running the bridge image, pinned by digest, for the runtime infra.stdio_runtime names. 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. One server process runs per client session, at the path /mcp on infra.port, on the compose network: nothing is published to the host, and provides.host is the compose service name. The healthcheck asks the bridge's /healthz endpoint with the wget the image carries. An edge from the tool, on a socket the author names, delivers the names its `inject:` block dictates into the bridge's environment, which the server inherits, or as files from compose configs. It delivers no credential to the server: an attachment on the server_env slot halts the build, because this target has no secret reference to deliver one through. A server that needs credentials runs under helm/mcp-stdio-bridge. Reach for this realization under Docker Compose; reach for helm/mcp-stdio-bridge on Kubernetes, for helm/mcp where the server ships as an image serving HTTP, and for compose/mcp-remote where someone else already runs it. 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:07ff189fd26d8b045dc86e6f901f3dc8ff7c64e5bb076e4515c55a8453e6db7e
- 发布时间
- 2026-11-10T10:19:41Z
- 签名身份
- 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:591fd30a5eb47c5b6d8ef183cdda98295c11731ffbd8087b5ddf081c3beb7e1d
此版本的引用
oci://hub.aggrega.ai/recipe/compose/mcp-stdio-bridge:1.0.0- 目标
- —
- 实现
- core/ai-tool/mcp:1.0.0
提供
此配方为使用方接入的确定性指针模板。
| 名称 | 模板 |
|---|---|
| host | {{ .context.instance_id }} |
| port | {{ .infra.port }} |
| endpoint | http://{{ .context.instance_id }}:{{ .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
所有必需输出均已满足,且提供的每个输出都在契约中列出。
被使用
目录中没有任何内容依赖此实体。