Skip to content

v3.0.0 - MCP SDK v2 / spec 2026-07-28

Choose a tag to compare

View all tags
@JamsusMaximus JamsusMaximus released this 30 Jul 17:36
· 9 commits to main since this release
v3.0.0
6b58f8d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The migration release

tp-mcp now runs on v2 of the MCP Python SDK, supporting the 2026-07-28 spec revision (stateless core, server/discover, cache metadata) while continuing to serve every earlier protocol revision from the same stdio server - old clients keep working, enforced by a CI job that drives the server with a pinned SDK 1.x client on every push.

Nothing about the tools changed

  • All 84 tools' inputs and outputs are identical: verified by a 60-tool live regression sweep against a pre-migration baseline - zero shape deltas
  • Stored credentials survive the upgrade untouched
  • Smoked end-to-end with current Claude Code against the release build

What you need to do

Pulling main (or this tag) is a major upgrade: re-run pip install -e . after pulling so the new mcp 2.x dependency installs. Minimum Python remains 3.10.

If you hit trouble: git checkout v2.2.0 && pip install -e . restores the last 2.x release. Critical fixes for the 2.x line will land on the v2.x branch. Report anything at #146.

Improvements riding along

  • Missing required arguments now return a readable INVALID_ARGS structured error (previously an SDK-level validation error; in raw v2 it would have been an opaque internal error)
  • The server reports its real version in serverInfo (previously unversioned on the wire)
  • tools/list carries spec-2026 cache metadata (ttlMs: 1h - the tool list is static)
  • TP_MCP_SKIP_STARTUP_VALIDATION=1 skips the startup auth check for offline/CI use

Roadmap: docs/mcp-2026-07-28-adoption-prd.md - next up is the MCP Apps work (inline fitness charts).

Assets 2
Loading