Adam Kocoloski 6787fb13ad Avoid sending null "params" in MCP notification (#54807) ... MCP servers that strictly validate the schema will reject notification requests with params:null. Zed needs to either send an empty object or omit the key altogether: https://modelcontextprotocol.io/specification/2024-11-05/basic/messages#notifications This one-line patch omits the key, consistent with the behavior in Request messages. I tested it with a dev build and confirmed that our internal MCP server now accepts Zed's "notifications/initialized" request, and Zed is subsequently able to discover the tools provided by this server. Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [ ] Unsafe blocks (if any) have justifying comments - [ ] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [ ] Tests cover the new/changed behavior - [ ] Performance impact has been considered and is acceptable Release Notes: - N/A		2026-05-06 13:33:06 +00:00
..
src	Avoid sending null "params" in MCP notification (#54807)	2026-05-06 13:33:06 +00:00
Cargo.toml	Fix MCP server processes leaking as zombies (#54793)	2026-05-06 13:30:07 +00:00
LICENSE-GPL	Factor tool definitions out of assistant (#21189)	2024-11-25 18:26:34 -05:00