mcp-connector changedagents-and-tools/mcp-connector
Nearest release: v2.1.308, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+4added
Lines−4removed
From line
498
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits32to this page, all time
The whole hunk
from line 498, old and new numbered
/
from line 498
498498
499499### MCP tool use block
500500
501```json
501```text wrap
502502{
503503 "type": "mcp_tool_use",
504504 "id": "mcptoolu_014Q35RayjACSWkSj4X2yov1",
from line 510
510510
511511### MCP tool result block
512512
513```json
513```text wrap
514514{
515515 "type": "mcp_tool_result",
516516 "tool_use_id": "mcptoolu_014Q35RayjACSWkSj4X2yov1",
from line 530
530530
531531When the API asks an MCP server for its tools while producing a response, the response starts with an `mcp_tool_listing` block for that server, one block for each server it asked:
532532
533```json
533```text wrap
534534{
535535 "type": "mcp_tool_listing",
536536 "mcp_server_name": "example-mcp",
from line 1996
19961996
199719971. **New beta header:** Change from `mcp-client-2025-04-04` to `mcp-client-2025-11-20`.
199819982. **Tool configuration moved:** Tool configuration now lives in the `tools` array as MCPToolset objects, not in the MCP server definition.
19993. **More flexible configuration:** New pattern supports allowlisting, denylisting, and per-tool configuration.
19993. **More flexible configuration:** The new pattern supports allowlisting, denylisting, and per-tool configuration.
20002000
20012001### Migration steps
20022002
No line in this hunk matches that.