v0.5.4 — MCP server modernization (Server → McpServer)

TL;DR

Maintenance release. No behavioral changes — refactors the MCP server's wiring under the hood from the deprecated low-level Server SDK class to the modern high-level McpServer API.

If you're already running v0.5.3, upgrading is drop-in safe — same tool names, same schemas, same behavior. No DB migration, no env changes.

Upgrade from 0.5.3

npm i -g github:VKirill/TencentDB-Memory-Claude-Code#v0.5.4
# Restart Claude Code (so MCP connection picks up the new server binary)

That's it. Scheduler, DB, env keys all unchanged.

Why

@modelcontextprotocol/sdk v1.29 marks the low-level Server class deprecated:

"Use McpServer instead for the high-level API. Only use Server for advanced use cases."

We're a plain stdio MCP exposing 4 tools — the canonical high-level use case. This release does the migration before SDK drops the deprecated class entirely.

Changes

Changed

• Migrated src/mcp/server.ts from low-level Server to high-level McpServer.
  • Dropped the manual setRequestHandler(ListToolsRequestSchema, ...) and setRequestHandler(CallToolRequestSchema, ...) switch dispatcher (~60 lines of boilerplate).
  • Each of the 4 tools (memory_search, conversation_search, recall_persona, recall_scenes) is now declared via a single server.registerTool(name, config, handler) call.
  • Zod schemas replace inline JSON Schema for input validation — McpServer auto-converts to draft-07 JSON Schema in the wire response (Claude Code accepts both draft-07 and 2020-12).
• Tool semantics preserved byte-equivalent: same names, same descriptions, same handler functions, same response shape (content: [{type:"text", text:...}]).

Added

• zod@4.4.3 promoted to direct production dependency. It was being used via transitive hoisting from @modelcontextprotocol/sdk and @ai-sdk/openai — fragile if either upstream drops it.

Verified

• 91/91 unit tests pass.
• JSON-RPC smoke test: initialize returns correct protocolVersion: 2025-06-18, capabilities.tools.listChanged: true, serverInfo: {name:tencentdb-memory, version:0.5.4}. tools/list returns all 4 tools with proper schemas.
• Audit against mcp-builder skill checklist:
  • ✅ No stdout pollution (grep clean)
  • ✅ Tool names follow SEP-986 (lowercase + underscores)
  • ✅ Capabilities advertised correctly (auto by SDK)
  • ✅ Error semantics correct (Tool Execution Error vs protocol error — SDK handles)
  • ✅ N/A: DNS-rebinding (stdio = local IPC only)