update

[wilsonwang371]

This pull request updates the MCP (Model Context Protocol) integration documentation and configuration to reflect the current implementation and clarify future directions. The main focus is on accurately describing how MCP servers are registered, how tools are injected and executed, and on updating configuration and timeout values. Significant improvements have been made to both English and Chinese documentation, including new troubleshooting and design documents, and the MCP registry configuration example.

Documentation Updates and Clarifications:

• Updated mcp-integration-architecture-en.md and mcp-integration-architecture-zh.md to describe the current MCP integration: MCP access is now via cchat only, with no separate mcp_* hostcalls, and only stdio transport is supported for MCP servers. The documentation now distinguishes between current features and future/planned work. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]

• Documented the new tool naming convention: tools are injected as mcp__<base64(server_id)>__<base64(tool_name)>, and routing also accepts the legacy mcp.<server_id>.<tool_name> format for compatibility. [1] [2] [3] [4] [5] [6]

• Added new documentation entries to INDEX.md for MCP integration architecture, task-level MCP subset design, and troubleshooting guides, improving discoverability of MCP-related docs. [1] [2]

Configuration and Example Updates:

• Updated the example MCP registry configuration: increased tool_timeout_ms from 8000ms to 30000ms, changed the command to use npx with the @modelcontextprotocol/server-filesystem package, and clarified config variable names and formats. [1] [2] [3]

These changes ensure the documentation and configuration accurately reflect the current state of MCP integration in the codebase and clarify the boundaries between what is implemented and what is planned for future work.