Omit icon sizes field for backward compatibility with older MCP clients #1645
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Removes the
sizesfield from icon definitions to fix connection failures with older MCP clients that expect a string instead of an array.Why
The 2025-11-25 MCP spec changed
Icon.sizesfrom a string to an array. The server uses SDK v1.2.0-pre.1 which implements the array format, but clients like Cursor v2.2.36 still expect a string, causing schema validation errors during initialization.What changed
Sizesfield inocticons.Icons()functionMCP impact
Tools with icons now omit the
sizesfield. Icons remain functional viasource(data URI) andmimeTypefields.Prompts tested (tool changes only)
Not applicable - change affects icon metadata only, not tool functionality.
Security / limits
Lint & tests
./script/lint./script/testDocs
Icon field is internal metadata; no user-facing documentation required.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.