Skip to content

v1.9.0 — MCP SDK v2 / spec 2026-07-28

Latest
Latest

Choose a tag to compare

View all tags
@dell-zhang dell-zhang released this 06 Aug 21:46
· 3 commits to main since this release
v1.9.0
f153eb1

TeleMem's MCP server is now built on the official MCP Python SDK v2 (mcp>=2.0.0,<3), implementing the current MCP specification (2026-07-28) while remaining compatible with legacy initialize-handshake clients.

Changed

  • MCP server migrated to mcp.server.mcpserver.MCPServer — the v1 SDK's FastMCP import path was removed upstream; the server now declares server-level metadata (title, version, website_url, icon).
  • Every MCP tool now carries the standard metadata from the 2025-11-25/2026-07-28 specs: a human-readable title, behavior annotations (readOnlyHint/destructiveHint/idempotentHint/openWorldHint), and a derived output schema; results are emitted as structuredContent (wrapped under a "result" key) alongside the unchanged JSON text content.
  • memory_history now returns {"memory_id": ..., "history": [...]} instead of a bare JSON array.
  • telemem.mcp.create_server() no longer takes host/port; pass them to server.run(transport="streamable-http", host=..., port=...).
  • --transport sse is deprecated (the MCP spec deprecated HTTP+SSE); it still works but logs a warning. Docs and the Docker image now show streamable-http.
  • examples/mcp_client.py uses the SDK v2 high-level mcp.client.Client; the MCP test suite drives both the modern (stateless) and legacy protocol paths.
  • server.json registry manifest: schema bumped to 2025-12-11.

Upgrade note: this release requires mcp>=2. If you embed the server via create_server(), move host/port from the constructor to run().

Full changelog: https://github.com/TeleAI-UAGI/telemem/blob/main/CHANGELOG.md

Assets 2
Loading