Skip to main content

​
New features

​
Automated session lifecycle management

The Supabase storage backend now includes built-in session cleanup powered by PostgreSQL’s pg_cron extension. Stale and abandoned sessions are automatically removed in two stages:
  • Short-term transient purge (every 5 minutes) — Cleans up failed or incomplete sessions whose TTL has expired, such as abandoned OAuth flows or connections that errored during setup.
  • Long-term dormancy eviction (daily) — Removes active sessions that haven’t been touched in 30+ days, preventing forgotten records from accumulating indefinitely.
Active sessions with ongoing usage are never affected by the short-term sweep, so persistent automation workflows and scheduled agents continue to work without interruption. The cleanup migrations are included automatically when you run npx mcp-ts supabase-init. See the Supabase storage guide for details.

​
Updates

​
Proactive session cleanup on connection failures

When a connection or authentication error occurs during setup, the session record is now cleaned up immediately rather than waiting for the next scheduled sweep. This keeps your database lean even in high-churn environments.

​
Improved release notes

GitHub releases for @mcp-ts/sdk now include auto-generated release notes with contributor attribution and a full changelog diff.