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. One service runs the bridge image, pinned by digest, for the runtime infra.stdio_runtime names, and starts the command line infra.stdio_command names; the launcher fetches the package when the server starts. One server process runs per client session, at the path /mcp on infra.port, where a consumer on the compose network reaches it at the service's name. Where the Release sets infra.published_port, that port on the host's loopback address, 127.0.0.1, forwards to infra.port; unset, nothing is published, and two servers that each publish take distinct published_port values. 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. The server's credentials arrive through the server_env slot: attach core/referenced-secret-set mapped to compose/dotenv-secret-set, each entry's value a Compose variable reference such as ${GITHUB_TOKEN}, which Docker Compose substitutes when the stack starts. An attachment publishing only a secret resource's name, or delivering no variable, halts the build. Reach for this realization under Docker Compose; reach for helm/mcp-stdio-bridge on Kubernetes, for compose/mcp or 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.

Version

1.0.01.1.0

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:37b13dda9ecf0b0d32453705b6b3766cfc4d399a9c22b3a1a8ddad05f769c23b
Published
2026-11-15T08:09:24Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/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:7582989b6c34c9eedf63521670ff10e52d6d65b5b6b1b9e67b578ef0309cbd80

Reference at this version

oci://hub.aggrega.ai/recipe/compose/mcp-stdio-bridge:1.1.0
Target
—
Implements
core/ai-tool/mcp:1.1.0

Provides

Deterministic pointer templates this recipe wires for consumers.

NameTemplate
host{{ .context.instance_id }}
port{{ .infra.port }}
endpointhttp://{{ .context.instance_id }}:{{ .infra.port }}{{ .locals.path }}
protocolhttp
credential_header

Workload

Workload · form: stateless · containers: main

Locals

NameTemplate
npm_imageghcr.io/supercorp-ai/supergateway:4.1.0@sha256:1938c43538a5308bce07d58028e9de00b7acfecb40b39b059b2f3931800ad910
pypi_imageghcr.io/supercorp-ai/supergateway:4.1.0-uvx@sha256:660c97d4ee58498f4654e1dc60682f4f4ccab363025c9b8b415d04b4e823025e
path/mcp
health_path/healthz
inject_file_config_prefix{{ .context.instance_id }}-file-

Values mapping

No values mapping declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

  • implementsimplementscontract compatible

    core/ai-tool/mcp:1.1.0

    All required outputs are satisfied and every provided output is named in the contract.

Used by

Nothing in the catalog depends on this entity.

Recipe concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy