MCP Server Upgraded to the 2026-07-28 Spec

Vist's MCP server now supports the 2026-07-28 protocol revision alongside the existing 2025-03-26 version — your current connection to Claude Desktop, Claude Code, or any other client keeps working exactly as before, with no reconnection needed.

What's new under the hood

• Stateless requests. Clients on the new spec no longer need the initialize/initialized handshake or an Mcp-Session-Id — every request now carries its own protocol version and capabilities.
• server/discover. A lighter-weight replacement for the old handshake, for clients that just need capability info up front.
• Cache hints on list results, so clients can stop re-fetching tool and resource definitions that rarely change.
• Stronger OAuth flow, including iss validation on authorization responses to guard against mix-up attacks.

Agent memory, opened up

While making agent identity work correctly under the new spec, we also removed an assumption that agent memory was Claude-only. Any MCP-compatible agent framework can now read and write to Vist's persistent memory layer, using its own agent name as identity — so your notes, tasks, and project context can follow you across tools, not just within one.

Read the full technical write-up on how we shipped dual-version support and what we learned along the way.