Skip to main content
Two releases shipped this week — v1.4.0 and v1.5.0 — bringing a cloud gateway, intelligent tool routing, four AI framework adapters, new storage options, and automated session cleanup.

​
New features

​
MCP Gateway v1.4.0

The new MCP Gateway lets you expose local MCP servers to cloud-based AI clients like ChatGPT and Claude. It creates a secure tunnel so remote assistants can reach tools running on your machine — no open ports or firewall changes required.
  • Install and run via uvx mcpassistant-gateway
  • Configure servers through a single mcp.json file
  • Manage all local-to-cloud connections through one persistent bridge
See the installation guide to get started.

​
Tool Router v1.4.0

You can now manage large tool catalogs with the Tool Router. Instead of injecting every tool schema into the LLM’s context window, the Tool Router offers three strategies:
  • all — Pass all tools through. Great for small projects.
  • search — Replace your tools with lightweight Meta-Tools that let the LLM discover, inspect, and execute tools on demand. Scales to 1,000+ tools with minimal token usage.
  • groups — Expose specific sets of tools based on application state or user intent.
The search strategy supports both keyword-based BM25 matching and optional semantic search via a custom embedding function.

​
AI framework adapters v1.4.0

Four new adapters make it easy to use MCP tools with popular AI frameworks:
  • AI SDK — Drop MCP tools into any Vercel AI SDK project.
  • LangChain — Use MCP tools as LangChain-compatible tools in chains and agents.
  • Mastra — Integrate MCP tools with the Mastra agent framework.
  • AG-UI — Connect MCP tools to remote agents via the AG-UI protocol, with built-in middleware for server-side tool execution.
Each adapter supports namespace prefixes to prevent name collisions when connecting to multiple MCP servers.

​
Automated session lifecycle management v1.5.0

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.

​
Supabase storage backend v1.4.0

Supabase is now available as a production-ready storage backend with PostgreSQL persistence, row-level security for tenant isolation, and application-level AES-256-GCM encryption for sensitive session fields. Auto-detects via the SUPABASE_URL environment variable and includes a built-in supabase-init CLI command to scaffold migrations.

​
MCP Documentation Server v1.4.0

The MCP Toolkit documentation is now available as a hosted MCP server. Add it to any MCP-compatible client — Claude Desktop, Cursor, or VS Code — to give your AI assistant direct access to search, browse, and read the full docs.

​
LocalStorage backend v1.4.0

A new LocalStorage backend persists sessions directly in the browser. Ideal for client-side apps and prototyping, with configurable namespaces, TTL-based expiration, and lazy eviction.

​
MCP App Host integration v1.4.0

MCP Apps now support a full App Host integration for rendering interactive tool UIs in sandboxed iframes — including resource preloading, fullscreen mode, host-guest sync for streaming and cancellation, and a custom loader prop.

​
Updates

​
Proactive session cleanup on connection failures v1.5.0

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.

​
Isomorphic storage architecture v1.4.0

Storage backends now work across both server and client environments. You can inject a storage backend directly into the MCP client via a storage option to swap between server-side backends (Redis, Supabase) and client-side backends (LocalStorage) without changing your application code.

​
Simplified MCP App rendering v1.4.0

You can now import McpAppRenderer and getMcpAppMetadata directly from the React client instead of going through the useMcpApps hook, giving you more control over where MCP App UIs are rendered.

​
Gemini CLI compatibility v1.4.0

The server now correctly responds to Gemini CLI’s streamable-http transport checks and MCP ping requests, so you can use MCP Toolkit with Google’s Gemini CLI without additional configuration.

​
Improved release notes v1.5.0

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

​
Bug fixes

  • OAuth handling — Improved OAuth flow reliability, including better callback handling and credential storage.
  • MCP Apps renderer stability — Fixed iframe white-screen flashes on load and stabilized client identity handling in the React renderer.
  • Tool name length violations — Resolved an issue where generated tool names could exceed protocol limits, causing connection failures.
  • Event routing — Fixed shared event routing so connection state updates are correctly reflected in the UI.
  • Storage proxy deadlock — Fixed a deadlock in the storage proxy that could cause hangs during backend initialization.