Yichen Jiang
545e2ad914
Node's built-in fetch ignores HTTP_PROXY, so every harness request connected directly regardless of what the user exported. Resolve one policy from the launch environment and install it as undici's global dispatcher, then wire the four surfaces a global dispatcher cannot reach: web_fetch's pinned transport, the OTLP exporter's node:http agent, the E2B SDK's own proxy option, and the environment a child process or worker thread is given. Each outbound call site carries an egress test that drives its real code path through a fake proxy; that measurement is what found the OTLP and E2B gaps.
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 Notes for the behavior decisions behind it.
- MCP client plugin Agent Note — the bridge's design: server-qualified naming, discovery, execution, and environment scrubbing.
- MCP client auto-reconnect Agent Note — the reconnect policy, the per-outage attempt budget, and the opt-out.
- Third-party memory MCP examples Agent Note — three default-off memory-server overlays delivered as reference configurations.
- 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.