跳到主要内容Skip to main content

工具 · 2026 增补 · 2026-11-18

Agent 工具的接线,在 2026 年换了四次Agent tool wiring changed four times in 2026

MCP Apps 让工具返回界面;Agent Skills 把能力打包成文件夹;AG-UI 补上 Agent 到用户的事件流;MCP 下一版把 session 从核心拿掉。四条都不是「新模型」,但都会改变工具站的选型。MCP Apps lets tools return a UI; Agent Skills packages capabilities as folders; AG-UI adds the agent-to-user event stream; the next MCP removes sessions from the core. None is a new model, but each changes tool selection.

只列有官方规范 / 官方公告的节点;协议版本不等于产品已采用。「候选」与「正式」分开写。Only nodes with an official spec or announcement; a protocol version does not mean adoption. “Candidate” and “final” are labelled separately.

工具对象Tool objects 265类目Categories 112026 协议Protocols 4
2026-01-26 MCP Apps 协议 / MCP 2026-10-22 Agent Skills 标准 / 技能 2026-11 AG-UI 1.0 协议 / 前端 2026-07-28 MCP 下一版 协议 / MCP 下一版
MCP Apps 与 Agent Skills 已有正式规范;MCP 下一版仍是候选。MCP Apps and Agent Skills have final specs; the next MCP is still a candidate.
2026-01-26协议 / MCPProtocol / MCP

MCP Apps:工具可以返回一个界面MCP Apps: a tool can return a UI

SEP-1865 定稿:工具结果可以带 ui:// 资源,客户端在沙箱 iframe 里渲染,并通过 JSON-RPC 回传交互;必须保留文本回退。SEP-1865 is final: a tool result can carry a ui:// resource, the client renders it in a sandboxed iframe and receives interactions over JSON-RPC; a text fallback is required.

规范spec
SEP-1865
资源resource
ui://
渲染render
sandboxed iframe
回退fallback
text required
为什么值得看Why it matters

它把「工具返回一段 JSON」升级为「工具返回一个可交互面板」,是 2026 年 Agent 工具体验最大的一次接口变化;图表、表单、审批都能在对话里完成。It upgrades “a tool returns JSON” to “a tool returns an interactive panel”, the biggest interface change for agent tools in 2026; charts, forms and approvals can happen inside the conversation.

边界 / 它没主张什么Boundary / what it does not claim

不是所有客户端都支持;iframe 带来权限与注入风险;文本回退是硬要求。它没主张「MCP Apps 取代普通工具调用」或「所有 UI 都能安全嵌入」。Not every client supports it; iframes bring permission and injection risk; text fallback is mandatory. It does not claim MCP Apps replaces ordinary tool calls, or that every UI can be embedded safely.

来源Sources:MCP Apps 官方博客MCP Apps official blog · MCP 规范MCP spec

2026-10-22标准 / 技能Standard / skills

Agent Skills:一个文件夹就是一项能力Agent Skills: a folder is a capability

2025-12 发布,2026-10-22 捐给 AAIF;用 SKILL.md + 脚本/资产描述一项可复用能力,按需加载,70+ 平台接入(厂商口径)。Released in December 2025 and donated to the AAIF on 2026-10-22; a reusable capability described by SKILL.md plus scripts/assets, loaded on demand, with 70+ platforms (vendor figure).

形态form
folder + SKILL.md
加载loading
progressive disclosure
治理governance
AAIF(2026-10-22)
平台platforms
70+(厂商口径)
为什么值得看Why it matters

它把「提示词 + 脚本 + 权限」打包成可移植单元,是工具站从「一个个 API」转向「一组组能力」的关键;对做内部 Agent 平台的人,比再写一个 prompt 模板更可维护。It packages prompt, scripts and permissions into a portable unit, the key shift from “APIs” to “capabilities”; for internal agent platforms it is more maintainable than another prompt template.

边界 / 它没主张什么Boundary / what it does not claim

SKILL.md 不是运行时,也不是安全沙箱;脚本权限仍由宿主决定;「70+ 平台」是厂商统计。它没主张「装上技能就自动安全」或「技能可以替代工具权限设计」。SKILL.md is not a runtime or a security sandbox; script permissions still belong to the host; “70+ platforms” is a vendor count. It does not claim installing a skill makes it safe, or that skills replace tool-permission design.

来源Sources:Anthropic 公告Anthropic announcement · Agent Skills 文档Agent Skills docs

2026-11协议 / 前端Protocol / frontend

AG-UI 1.0:Agent 到用户的事件流AG-UI 1.0: an event stream from agent to user

一条有序事件流,把 token、工具调用、共享状态与中断送到前端;HTTP + SSE,定义 RunAgentInput 与事件类型。One ordered event stream carrying tokens, tool calls, shared state and interrupts to the frontend; HTTP + SSE, with RunAgentInput and typed events.

规范spec
AG-UI 1.0
传输transport
HTTP + SSE
输入input
RunAgentInput
定位role
Agent ↔ 用户
为什么值得看Why it matters

MCP 管工具、A2A 管 Agent 之间,AG-UI 补上「Agent 怎么把过程展示给人」;做聊天式 Agent 前端时,它比自造 WebSocket 事件协议更可维护。MCP handles tools, A2A handles agent-to-agent; AG-UI adds how an agent shows its process to a person. For chat-style agent frontends it is more maintainable than a home-grown WebSocket event protocol.

边界 / 它没主张什么Boundary / what it does not claim

它是事件协议,不是模型或运行时;SSE 不等于适合所有场景(双向低延迟可换其他传输);1.0 不等于所有前端框架已适配。它没主张「取代 MCP / A2A」。It is an event protocol, not a model or runtime; SSE is not right for every case (use another transport for low-latency bidirectional); 1.0 does not mean every frontend framework is adapted. It does not claim to replace MCP or A2A.

来源Sources:AG-UI 文档AG-UI docs

2026-07-28协议 / MCP 下一版Protocol / next MCP

MCP 下一版:无状态核心 + 扩展Next MCP: stateless core + extensions

2026-07-28 规范候选把协议级 session 从核心移除,改为无状态请求;Extensions 与 Tasks 作为可选能力,降低水平扩展与多租户接入成本。The 2026-07-28 spec candidate removes protocol-level sessions from the core in favour of stateless requests; Extensions and Tasks become optional capabilities, lowering horizontal-scaling and multi-tenant costs.

版本version
2026-07-28 RC
核心core
stateless
扩展extensions
Extensions / Tasks
状态status
候选
为什么值得看Why it matters

无状态核心让 MCP 服务器更像普通 HTTP 服务,能直接放进负载均衡与多租户网关;对工具站里 32 个 MCP 对象,这是部署方式的改变,不只是协议细节。A stateless core makes MCP servers look more like ordinary HTTP services that fit load balancers and multi-tenant gateways; for the 32 MCP objects on the tools site, it changes deployment, not just spec detail.

边界 / 它没主张什么Boundary / what it does not claim

这是候选版本,不是已冻结标准;session 状态移到应用层,意味着应用要自己管会话与重放;Tasks 仍是扩展,客户端支持度不齐。它没主张「MCP 不再需要状态」或「所有服务器都应改成无状态」。A candidate, not a frozen standard; moving session state to the application means the app must handle sessions and replay; Tasks is still an extension with uneven client support. It does not claim MCP no longer needs state, or that every server should go stateless.

来源Sources:MCP 规范MCP spec · MCP 博客MCP blog