gengruilin
5a30774840
The Settings management page this manager was built for is not shipping, and
every connector plugin registers its server. Remove what only that page used:
- mcp-manager: the volatile `servers` configuration and its write-time
validation, stdio entries, the `enabled` flag, the `probe` operation, and the
`mcp-manager/status` event. A registration takes a Streamable HTTP `url`, and
a `startupTimeoutMs` setting bounds each registered server's startup.
- mcp-client: `${credential:REF}` templates (`expandTemplates`), the
`waiting-credentials` state, `probeServer`, and the exports that existed only
for the manager's write-time validation.
The Web profile mounts the manager without injecting credentials, and the
`mcp-template-error` snapshot goes with the templates.
description, kind
| description | kind |
|---|---|
| The MCP package group: connect external Model Context Protocol servers, call their tools, and read their resources. | package-group |
MCP — Model Context Protocol
English | 中文
Summary
The mcp/ group lets the model call external Model Context Protocol (MCP) tools and read server resources. Configure mcp-client entries directly; installed plugins register their servers with mcp-manager. Shipped profiles already mount mcp-resources once. MCP tools and prompt text appear only for callers with a configured server in scope. Connections also supply server instructions. Package READMEs own configuration and limitations.
Table of Contents
Packages
The client owns each configured connection, the manager runs the clients that plugins register, and the shared resource package supplies resource tools across those connections.
| Package | What it provides |
|---|---|
mcp-client/ |
Connect one MCP server, expose its tools and instructions, and provide its resource operations |
mcp-manager/ |
Run the mcp-client instances that plugins register, with status, restart, and a server-list stream |
mcp-resources/ |
Discover and read resources through shared tools with explicit server selection |
Related documentation
Try the worked example configurations to see the plugin in action, then read the Agent Note for the behavior decisions behind it.
- historical MCP client plugin Agent Note — the bridge's design: server-qualified naming, discovery, execution, and environment scrubbing.
- MCP manager Agent Note — plugin-registered servers: reconcile semantics, status surface, and rejected alternatives.
- Resources and instructions reference — on-demand resource access and scoped server guidance.
- Third-party memory MCP guide — runnable overlay rows and setup instructions.
- Tools subsystem reference — the
ToolRuntimethat receives the registered tools.
Dev Note
Working context for maintainers — click to expand
None.