Turtle
e7def469e1
* feat(i18n): key translation pairing records by heading section Replace the whole-file blob hashes in *.i18n.yaml with one entry per heading section that still holds language-specific content, keyed by the English heading-slug path. Blocks identical across the pair (generated table rows, code blocks, shared regions) stay out of the hash, so edits to different sections and identical regenerations merge with Git's default text merge, including on GitHub. Remove the dsh-translation-pairing merge driver, its resolver command and installer wiring; gen-translation-brief recovers last-confirmed text from commit history. Migrate all active records, archive the superseded Agent Note, and record the replayed conflict reduction in the new one. * test(i18n): refresh translation prompt snapshot for the terminology note * feat(i18n): exclude only code blocks and generated regions from pairing records Replace byte-equality masking with an explicit rule: a record hash skips fenced code blocks and BEGIN/END GENERATED regions, the two kinds of content the pairing gate already requires to be identical on both sides. Move generated data into regions written into both pages: gen-config-catalog renders both languages and the record with per-package regions labelled by code identifiers; gen-module-graph keeps its table in a region; gen-doc-graphs splices the event matrix regions into the Chinese page. Add a generic region splice beside the region grammar.
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 only mcp-client entries; 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 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-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.
- MCP client plugin Agent Note — the bridge's design: server-qualified naming, discovery, execution, and environment scrubbing.
- Resources and instructions Agent Note — 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.