Component

core/ai-tool/mcp

A tool that attaches a Model Context Protocol server to an agent, so the tools that server publishes become available to the agent without each one being declared separately in the catalog. The server is reached over HTTP, and the software behind it is the Release's, so a server can be wired to an agent without a catalog entity of its own. Marked mutating, because what an attached server exposes is decided by that server rather than by this declaration. Every realization publishes a host, port, endpoint, protocol and credential header, so an agent wires to the tool the same way whichever one answers it. Which realization to reach for follows how the server is published. Where it ships as a container image serving the protocol over HTTP, reach for helm/mcp on Kubernetes or compose/mcp for local development, which run the image infra.image names. Where it is an npm or PyPI package speaking only stdio, reach for helm/mcp-stdio-bridge on Kubernetes or compose/mcp-stdio-bridge for local development, which run the command line infra.stdio_command names inside a pinned bridge serving it over HTTP. Where someone else already runs it, reach for helm/mcp-remote or compose/mcp-remote, which run nothing and publish the address infra.endpoint names. A server's own credentials arrive through the server_env slot, on the realizations that run a server, helm/mcp aside. An edge from the tool, on a socket the author names, delivers what its `inject:` block dictates, as variables or as files, wherever a server runs; the mcp-remote realizations run nothing and refuse one. helm/mcp and compose/mcp deliver the component's own `inject:` block; the others refuse it.

Version

1.0.01.1.0

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:dcd44d71ac50183862bace86bae045bf5c127482dca7418876e9e434265a135a
Published
2026-11-15T08:08:58Z
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:1e21659db02318ed246d4698aee304a20090ee6a14662b845c9b4cdc790d1452

Reference at this version

oci://hub.aggrega.ai/component/core/ai-tool/mcp:1.1.0

Developer parameters

Values the developer sets in the Aggregate.

Extends BaseComponents#/schemas/BaseToolParameter

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—noContainer image serving the Model Context Protocol over HTTP. Read by helm/mcp and compose/mcp, which require it; the mcp-stdio-bridge realizations run the bridge image they pin, and the mcp-remote realizations run nothing, so both refuse this key.
stdio_commandarray (min 1)—noThe server's command line, one list item per argument, for example [npx, -y, "@modelcontextprotocol/server-everything"] for an npm package or [uvx, mcp-server-fetch] for a PyPI package. Each item reaches the server exactly as written. Read only by the mcp-stdio-bridge realizations; the others refuse it.
stdio_runtimestring (npm | pypi)—noThe package ecosystem the command line runs from, selecting the bridge image that carries its launcher: npm runs on Node.js with npm and npx; pypi adds Python, uv and uvx. Read only by the mcp-stdio-bridge realizations; the others refuse it.
endpointstring—noThe http or https URL a client connects to a server someone else already runs at, for example https://mcp.example.com/mcp, without any part that carries a key: at least its scheme and host. Read only by the mcp-remote realizations, which publish it as written and read host, port and protocol from it; the others refuse it. A consumer whose server reads its key from the address supplies the whole address through the endpoint slot on its own connection to the tool.
credential_headerstringAuthorizationnoThe request header the server reads a caller's credential from, which the realization publishes for a consumer to present its credential under. Read by helm/mcp, compose/mcp and the mcp-remote realizations; the mcp-stdio-bridge realizations publish an empty header instead.
portinteger (min 1024, max 65535)8080noPort the tool listens on, and the port it publishes to consumers. The mcp-remote realizations publish the port infra.endpoint names instead.
published_portinteger (min 1024, max 65535)—noPort published on the host's loopback address, 127.0.0.1, on Docker Compose, forwarding to infra.port inside the container; any process on this machine can reach it there. Unset, nothing is published. Kubernetes realizations refuse it; reach the Service with kubectl port-forward, or attach core/public-ingress.
computeobject—no—

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesDNS name an agent calls to reach the protocol server: the Service's name on Kubernetes, the service's name on the compose network, or the host infra.endpoint names under the mcp-remote realizations. A consumer that composes its own address dials this name; one that does not reads `endpoint` instead.
portinteger—yesTCP port the protocol server is reached on. It follows the port an operator set in the Release — under the mcp-remote realizations, the port infra.endpoint names, or its scheme's default port where it names none — so a consumer reads it rather than assuming a default.
endpointstring—yesFull base URL an agent connects to the protocol server at, with the host and the port already composed, and the path too where the realization fixes the one the server answers at, as the bridge realizations do; under the mcp-remote realizations it is infra.endpoint as the Release wrote it, the address without any part that carries a key. It is the address a client library needs in order to discover the tools that server publishes. Where the server reads its key from its address, a consumer reads the whole address from the endpoint slot on its own connection to the tool instead.
protocolstring—noURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.
credential_headerstring—noThe request header a consumer presents its credential under, where the server checks one: Authorization unless the Release names another in infra.credential_header. The credential itself is the consumer's, held on its own connection to the tool. Empty under the mcp-stdio-bridge realizations, whose bridge checks no caller's credential.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

SlotSelectorRequiredInjectSensitiveDescription
server_envfeature.aggrega.ai/kind=secretnoenvyesEnvironment variables the server reads its credentials from, one per variable the server reads. On Kubernetes, helm/mcp-stdio-bridge imports every data key of the Secret the attachment names into the bridge's environment by reference: attach core/referenced-secret mapped to helm/k8s-existing-secret to name a Secret that already exists, and the credential stays out of every rendered file; core/referenced-secret-set's realization writes the values into a Secret the build renders, which suits evaluation. On Docker Compose, compose/mcp-stdio-bridge and compose/mcp write each variable into the service's environment: attach core/referenced-secret-set mapped to compose/dotenv-secret-set, each value a Compose variable reference such as ${GITHUB_TOKEN}. helm/mcp and the mcp-remote realizations refuse an attachment.

Self-inject allowlist

env, file

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

Used by

Component 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