Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
description, kind
| description | kind |
|---|---|
| The MCP package group: attach external Model Context Protocol servers so their tools are callable as native tools. | package-group |
MCP — Model Context Protocol
English | 中文
Summary
The mcp/ group connects the harness to the Model Context Protocol (MCP) ecosystem of tool servers. The one package in this group attaches an external server — a filesystem, GitHub, database, or memory server — so its tools are available to the model as native tools under stable server-qualified names. Each server is one configuration entry; nothing ships enabled, so you opt in per server. Only the Tools capability is bridged: MCP resources and prompts are not supported. This page maps the group; the package README owns the per-package contract.
Table of Contents
Packages
The group holds one package; the package README and the links below own the details.
| Package | What it provides |
|---|---|
mcp-client/ |
Attach one external MCP server so the model can call its tools as native tools |
Related documentation
Try the worked example configurations to see the plugin in action, then read the Agent Note for the behavior decisions behind it.
- MCP client plugin Agent Note — the bridge's design: server-qualified naming, discovery, execution, and environment scrubbing.
- 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.