@@ -58,29 +58,32 @@ Preferred plugin path is npm package distribution plus local extension loading f
5858If you build a plugin, host and maintain it in your own repository.
5959The bar for adding optional plugins to core is intentionally high.
6060Plugin docs: [`docs/tools/plugin.md`](docs/tools/plugin.md)
61-Community plugin listing + PR bar: https://docs.openclaw.ai/plugins/community
61+Community plugin listing + PR bar: [`docs/plugins/community.md`](docs/plugins/community.md)
62626363Memory is a special plugin slot where only one memory plugin can be active at a time.
6464Today we ship multiple memory options; over time we plan to converge on one recommended default path.
65656666### Skills
67676868We still ship some bundled skills for baseline UX.
69-New skills should be published to ClawHub first (`clawhub.ai`), not added to core by default.
69+New skills should be published to [ClawHub](https://clawhub.ai/) first, not added to core by default.
7070Core skill additions should be rare and require a strong product or security reason.
71717272### MCP Support
737374-OpenClaw supports MCP through `mcporter`: https://github.com/steipete/mcporter
74+OpenClaw has first-class MCP support in core.
75+MCP docs: [`docs/cli/mcp.md`](docs/cli/mcp.md)
757676-This keeps MCP integration flexible and decoupled from core runtime:
77+Current core surfaces:
777878-- add or change MCP servers without restarting the gateway
79-- keep core tool/context surface lean
80-- reduce MCP churn impact on core stability and security
79+- `openclaw mcp serve` exposes OpenClaw-backed channel conversations to Codex, Claude Code, and other MCP clients.
80+- `openclaw mcp list|show|set|unset` manages OpenClaw-owned outbound MCP server definitions under `mcp.servers`.
81+- Embedded Pi can materialize configured MCP servers as agent tools, filtered through the same owner/tool-policy pipeline as other tools.
82+- CLI backends can opt into bundle MCP overlays so Codex, Claude, Gemini, and similar CLIs receive scoped Gateway tools through a loopback MCP bridge.
83+- ACPX integrations can expose selected OpenClaw tools through explicit MCP bridges.
818482-For now, we prefer this bridge model over building first-class MCP runtime into core.
83-If there is an MCP server or feature `mcporter` does not support yet, please open an issue there.
85+`mcporter` is still useful for direct MCP server inspection, ad-hoc calls, generated CLIs, and specialized integrations such as QMD keep-alive.
86+It is no longer the only OpenClaw MCP integration path.
84878588### Setup
8689@@ -98,11 +101,11 @@ It is widely known, fast to iterate in, and easy to read, modify, and extend.
9810199102## What We Will Not Merge (For Now)
100103101-- New core skills when they can live on ClawHub
104+- New core skills when they can live on [ClawHub](https://clawhub.ai/)
102105- Full-doc translation sets for all docs (deferred; we plan AI-generated translations later)
103106- Commercial service integrations that do not clearly fit the model-provider category
104107- Wrapper channels around already supported channels without a clear capability or security gap
105-- First-class MCP runtime in core when `mcporter` already provides the integration path
108+- MCP work that duplicates existing `openclaw mcp`, bundle-MCP, ACPX bridge, or `mcporter` paths without a clear product or security gap
106109- Agent-hierarchy frameworks (manager-of-managers / nested planner trees) as a default architecture
107110- Heavy orchestration layers that duplicate existing agent and tool infrastructure
108111此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。