improvementmcp
MCP v2 support
Fewer round trips and native support for the new MCP v2 protocol.
MCP shipped a major protocol revision, and the agimem MCP server supports it today. As agent clients (Claude Desktop, Cursor, VS Code, and others) upgrade to it, you'll get a smoother connection to your memories:
- Fewer round trips to get started. The old protocol required a full handshake before an agent could do anything else. v2 requests are self-describing, so a client can go straight to listing or calling tools without that extra back-and-forth first — especially the first time an agent talks to a fresh capsule.
- Speaks the new protocol natively. Requests using the 2026-07-28 revision are served directly, not through a legacy compatibility shim, so clients that have moved to it get the behavior the spec actually describes.
- Ready for what's next. As more of your tools move to MCP v2 clients, agimem keeps working without you having to reconfigure anything.
Do I need to do anything?
No. Clients on the older protocol keep connecting exactly as before — this is a behind-the-scenes upgrade with no changes to tool names, inputs, or output formats.