Dylan 094d7af8c3 [mcp-server] Populate notifications._meta with requestId (#1704) ... ## Summary Per the [latest MCP spec](https://modelcontextprotocol.io/specification/2025-06-18/basic#meta), the `_meta` field is reserved for metadata. In the [Typescript Schema](0695a497eb/schema/2025-06-18/schema.ts (L37-L40)), `progressToken` is defined as a value to be attached to subsequent notifications for that request. The [CallToolRequestParams](0695a497eb/schema/2025-06-18/schema.ts (L806-L817)) extends this definition but overwrites the params field. This ambiguity makes our generated type definitions tricky, so I'm going to skip `progressToken` field for now and just send back the `requestId` instead. In a future PR, we can clarify, update our `generate_mcp_types.py` script, and update our progressToken logic accordingly. ## Testing - [x] Added unit tests - [x] Manually tested with mcp client		2025-07-28 13:32:09 -07:00
..
src	[mcp-server] Populate notifications._meta with requestId (#1704)	2025-07-28 13:32:09 -07:00
tests	Serializing the eventmsg type to snake_case (#1709)	2025-07-28 10:26:27 -07:00
Cargo.toml	fix: move arg0 handling out of codex-linux-sandbox and into its own crate (#1697)	2025-07-28 08:31:24 -07:00