Skip to content

v0.0.30

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Sep 19:18
v0.0.30
e4e1557
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

MCP protocol revision 2026-07-28. VoidLLM now speaks the new MCP revision alongside the previous one on the same endpoints, as MCP server, as MCP client and as a transparent gateway. The protocol version is negotiated per request and can be pinned per MCP server. (#219)

  • Pagination: tool listings from upstream MCP servers follow nextCursor, so servers with many tools are no longer cut off after the first page.
  • Live tool updates: with Code Mode enabled, VoidLLM listens for tool changes on upstreams that support subscriptions/listen and refreshes their tools right away instead of waiting for the cache TTL. The built-in Code Mode server offers the same subscriptions/listen to its own clients.
  • Streaming: MCP responses are streamed through instead of buffered, with an idle timeout and a byte cap.

Upgrade notes

  • Breaking - MCP browser origins: MCP endpoints accept a browser Origin header only if it is listed in settings.mcp.allowed_origins. Without a list, only localhost origins are accepted. If you serve MCP to a browser under your own domain, add it to allowed_origins. SDK and CLI clients (no Origin header) are unaffected.
  • A database migration adds the per-server MCP protocol version. It runs automatically on startup.
  • server.proxy.write_timeout: 0 is not supported and falls back to 120s. For long-lived MCP streams set an explicit value such as 1h. In dual-port mode MCP streams are capped at 120s and end gracefully, clients reconnect.

Full changelog: v0.0.29...v0.0.30

Assets 8
Loading