You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix MCP endpoint thread_id to use valid MongoDB ObjectId
- Changed thread_id from ISO timestamp format to valid ObjectId
- MongoDB expects 24-character hex string for ObjectId
- Fixes error: 'mcp_2025-08-16T06:43:58...' is not a valid ObjectId
- Updated tests to verify ObjectId format
0 commit comments