doc: Updated documentation to version v2.2.0

Author: Amery2010

CHANGELOG.md

@@ -7,6 +7,31 @@ group changes under a level-2 heading that matches the release tag, such as
 `## v2.0.0`; the release workflow uses that section as the GitHub release notes
 when the matching tag is pushed.
 
+## v2.2.0
+
+- **New capabilities:** Added native Anthropic Messages API support through the
+  official SDK, including provider-specific streaming and tool-call handling.
+- **MCP integration:** Added remote `streamable-http` MCP server discovery from
+  the official MCP Registry, custom server installation, header authentication,
+  tool registration, server-side execution, caching, pagination, and hosted URL
+  safety controls. Local stdio, npm, Docker, and OAuth transports remain out of
+  scope for this version.
+- **Reliability and security:** Strengthened API route access policy, request
+  body and response limits, terminal stream validation, context budgeting and
+  compression, outbound URL/DNS checks, shared plugin registration, and Worker
+  gzip-size and deployment dry-run validation.
+- **Architecture and maintainability:** Split the chat shell, composer,
+  message editor, Markdown diagram rendering, and chat-service orchestration
+  into smaller components, hooks, and domain modules while preserving the
+  existing user-facing workflows.
+- **Fixes and experience:** Fixed known issues across branch-preserving chat
+  history, tool-call completion, provider response handling, image/export
+  fallback, memory/RAG/search/voice workflows, settings, loading/error states,
+  and accessibility behavior.
+- **Engineering and documentation:** Aligned local, CI, Docker, and Worker
+  guidance around Node 22 and pnpm 10.30.3, added artifact-hygiene checks, and
+  synchronized Anthropic, MCP, privacy, security, and deployment documentation.
+
 ## v2.1.0
 
 - Rebuilt System Settings with clearer grouped controls, an About panel,

README.md

@@ -20,9 +20,23 @@
   <img alt="TypeScript" src="https://img.shields.io/badge/TypeScript-5-3178c6" />
 </p>
 
-Neo Chat is a self-hostable, local-first AI chat application built with Next.js, React, TypeScript, and Zustand. It brings multi-provider chat, assistant presets, text-only Skills, OpenAPI-style plugin tools, web search, knowledge-base RAG, local memory, voice, generated media, rich message rendering, citations, and editable artifacts into one clean workspace.
-
-It is designed for people who want the power of modern AI workspaces without giving up local data ownership. Chat history, workspace metadata, skills, plugin configuration, memories, and files stay in the browser by default; server routes act as controlled proxies for model providers, search, RAG, document parsing, voice, plugin execution, and deployment health.
+Neo Chat is a self-hostable, local-first AI chat application built with Next.js, React, TypeScript, and Zustand. It brings multi-provider chat, assistant presets, text-only Skills, OpenAPI-style plugin tools, remote streamable HTTP MCP servers, web search, knowledge-base RAG, local memory, voice, generated media, rich message rendering, citations, and editable artifacts into one clean workspace.
+
+It is designed for people who want the power of modern AI workspaces without giving up local data ownership. Chat history, workspace metadata, skills, plugin configuration, memories, and files stay in the browser by default; server routes act as controlled proxies for model providers, search, RAG, document parsing, voice, plugin and MCP execution, and deployment health.
+
+## v2.2.0 Highlights
+
+- Added native Anthropic Messages API support through the official SDK.
+- Added remote streamable HTTP MCP server discovery and installation from the
+  official MCP Registry, with plugin-market management, authentication, and
+  server-side tool execution. This release intentionally supports remote MCP
+  servers only.
+- Strengthened provider requests, API route policy, context budgeting,
+  outbound URL safety, plugin registration, and Worker deployment validation.
+- Reconstructed the chat shell, composer, message rendering, and chat service
+  internals into smaller modules while preserving existing workflows.
+- Fixed known issues across chat history, tool calls, provider streams, media
+  and exports, memory/RAG/search/voice flows, settings, and accessibility.
 
 ## v2.1.0 Highlights
 

README.zh-CN.md

@@ -20,9 +20,22 @@
   <img alt="TypeScript" src="https://img.shields.io/badge/TypeScript-5-3178c6" />
 </p>
 
-Neo Chat 是一个可自托管、本地优先的 AI 对话应用，基于 Next.js、React、TypeScript 和 Zustand 构建。它把多供应商模型、助理预设、纯文本技能、OpenAPI 风格插件工具、联网搜索、知识库 RAG、本地记忆、语音、生成媒体、富消息渲染、引用和可编辑产物整合到一个干净的工作台中。
-
-它适合想使用现代 AI 工作台、同时保持本地数据所有权的用户。默认情况下，对话历史、工作区元数据、技能、插件配置、记忆和文件都保存在浏览器内；服务端路由作为受控代理，连接模型供应商、搜索、RAG、文档解析、语音、插件执行和部署健康检查。
+Neo Chat 是一个可自托管、本地优先的 AI 对话应用，基于 Next.js、React、TypeScript 和 Zustand 构建。它把多供应商模型、助理预设、纯文本技能、OpenAPI 风格插件工具、远程 streamable HTTP MCP 服务器、联网搜索、知识库 RAG、本地记忆、语音、生成媒体、富消息渲染、引用和可编辑产物整合到一个干净的工作台中。
+
+它适合想使用现代 AI 工作台、同时保持本地数据所有权的用户。默认情况下，对话历史、工作区元数据、技能、插件配置、记忆和文件都保存在浏览器内；服务端路由作为受控代理，连接模型供应商、搜索、RAG、文档解析、语音、插件与 MCP 执行和部署健康检查。
+
+## v2.2.0 亮点
+
+- 通过官方 SDK 新增 Anthropic 原生 Messages API 支持。
+- 新增从官方 MCP Registry 发现和安装远程 streamable HTTP MCP 服务器，
+  支持插件市场管理、鉴权和服务端工具执行；本版本明确只支持远程 MCP
+  服务器。
+- 加强供应商请求、API 路由策略、上下文预算、出站 URL 安全、插件注册表
+  和 Worker 部署校验。
+- 将聊天壳层、输入框、消息渲染和聊天服务内部拆分为更小的模块，同时保持
+  现有用户流程。
+- 修复聊天历史、工具调用、供应商流式响应、媒体与导出、记忆/RAG/搜索/语音、
+  设置和无障碍相关的已知问题。
 
 ## v2.1.0 亮点
 

docs/deployment-hardening.md

@@ -188,6 +188,13 @@ a plugin is enabled for a chat, runtime tool calls execute automatically without
 a per-call confirmation modal. See [Reliability and Safety Model](reliability-and-safety.md)
 for tool execution boundaries, context budgeting, and recovery behavior.
 
+Remote MCP servers use the same server-registered plugin path and outbound URL
+policy. Neo Chat v1 supports only remote `streamable-http` MCP over HTTPS;
+hosted deployments block localhost and private-network MCP targets unless
+`ALLOW_LOCAL_NETWORK_PROXY=true` is explicitly enabled. Hosted or multi-instance
+deployments should configure `PLUGIN_REGISTRY_STORE=upstash` so installed MCP
+tools resolve consistently across instances.
+
 ## Deployment Health
 
 Settings includes a deployment health panel backed by `/api/health`. The route

docs/privacy-and-local-data.md

@@ -73,6 +73,12 @@ plugin requests, and BYOK envelopes. Local memory tool results may also be
 present in model request context. Deployments should treat server logs,
 observability tools, and hosting provider logs as sensitive.
 
+Remote MCP calls send model-generated tool arguments, including any context the
+tool arguments contain, to the configured MCP server. MCP tool results return
+through the plugin execution route and may be included in a subsequent model
+request. Treat every MCP server as a third-party service with its own logging,
+retention, and external side-effect behavior.
+
 Neo Chat validates request payloads, applies URL safety gates, limits response
 sizes, and uses hosted-mode restrictions, but upstream providers still receive
 the content required to complete user-requested actions.
@@ -86,6 +92,8 @@ Depending on configuration, user content may be sent to:
 - RAG/vector services and document parsers such as Mineru or LlamaParse.
 - Voice providers such as ElevenLabs or Mimo.
 - Plugin APIs enabled by the user.
+- Remote MCP servers installed from the Registry or configured through a custom
+  HTTPS endpoint.
 
 Text-only skills themselves are local prompt instructions, but applied skill
 content can be sent to the selected model provider as part of the prompt.

docs/reliability-and-safety.md

@@ -54,6 +54,14 @@ policy, response limits, and the configured tool-call round ceiling. Hosted
 deployments still require server-registered plugins; client-submitted legacy
 plugin definitions remain blocked.
 
+MCP-backed functions add a remote side-effect boundary: the MCP server owns the
+tool implementation and may perform external actions. The supported MCP
+transport is remote `streamable-http` over HTTPS. Installation and execution
+use the same server-side plugin registration, outbound URL policy, response
+limits, and hosted local-network restrictions as other network-capable
+plugins. MCP results are also bounded before they enter tool details or later
+model context.
+
 Built-in plugin IDs are reserved. Custom or manifest-installed plugins cannot
 override them, and built-ins take precedence if a stale mutable registry entry
 uses the same ID. If multiple active plugins expose the same function name, tool

package.json

@@ -2,7 +2,7 @@
   "name": "neo-chat",
   "description": "An omni AI chat application with a clean UI and excellent performance.",
   "private": true,
-  "version": "2.1.0",
+  "version": "2.2.0",
   "license": "MIT",
   "packageManager": "pnpm@10.30.3",
   "type": "module",