本页面为机器翻译。阅读英文原文。

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.

版本

1.0.01.1.0

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:dcd44d71ac50183862bace86bae045bf5c127482dca7418876e9e434265a135a
发布时间
2026-11-15T08:08:58Z
签名身份
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:1e21659db02318ed246d4698aee304a20090ee6a14662b845c9b4cdc790d1452

此版本的引用

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

开发者参数

开发者在 Aggregate 中设置的值。

扩展 BaseComponents#/schemas/BaseToolParameter

运维规格

运维人员按环境调整的基础设施规格。

名称类型默认值必需描述
imagestring—否Container 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)—否The 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)—否The 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—否The 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_headerstringAuthorization否The 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)8080否Port 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)—否Port 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—否—

输出契约

此组件通过 uses 拓扑向使用方发布的值。

名称类型默认值必需描述
hoststring—是DNS 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—是TCP 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—是Full 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—否URL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.
credential_headerstring—否The 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 套接字

此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。

未声明 uses 套接字。

附加槽位

Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。

槽位选择器必需注入敏感描述
server_envfeature.aggrega.ai/kind=secret否env是Environment 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.

自注入允许列表

env, file

关系

与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。

使用

被使用

Component 概念参考 →

Aggrega 目录 — 收录组件、功能、配方以及渲染它们的插件的开放索引。

基于共享的 Aggrega 设计系统构建。

隐私