Skip to content

Releases ​

The current stable release is @anvia/mcp 1.2.3.

VersionSummary
1.2.3Refreshed the package README.
1.2.2Updated @modelcontextprotocol/client to ^2.1.0 and undici to ^8.11.2.
1.2.1Updated undici to ^8.11.0.
1.2.0Bounded Streamable HTTP responses per JSON-RPC message with the new transport.maxBufferSize option (default 10 MiB, applied to a regular response body and to each SSE event, in both SSRF modes; custom transports stay caller-owned).
1.1.3Declared compatible workspace peer ranges so additive internal dependency releases do not force major releases of dependents.
1.1.2Updated the Core dependency to 1.1.2.
1.1.1Bumped upstream runtime dependencies and aligned zod to 4.5.4 across packages.
1.0.11Updated the Core dependency to 1.0.10.
1.0.10Allow versionNegotiation on McpClient so applications can connect to 2025-era servers with mode: "auto" or mode: "legacy". The default remains a strict 2026-07-28 pin with no fallback.
1.0.9Updated the Core dependency to 1.0.9.
1.0.8Updated the Core dependency to 1.0.8.
1.0.7Updated the Core dependency to 1.0.7.
1.0.6Updated the Core dependency to 1.0.6.
1.0.5Declared and verified Bun 1.3.14 runtime compatibility for MCP HTTP/SSE and stdio transports.
1.0.4Updated the Core dependency to 1.0.4.
1.0.3Updated the Core dependency to 1.0.3.
1.0.2Updated the Core dependency to 1.0.2.
1.0.1Updated the Core dependency to 1.0.1.
1.0.0Extracted MCP connection ownership from Core and adopted the split official MCP TypeScript SDK v2 packages with required protocol 2026-07-28 and no legacy fallback.

Applications upgrading from earlier RCs must install @anvia/mcp and change client imports from @anvia/core/mcp. The default still pins protocol 2026-07-28. Configure versionNegotiation on McpClient when a 2025-era server needs mode: "auto" or mode: "legacy". Core continues to expose the lightweight MCP registration types consumed by Agent.

Read the source changelog and @anvia/mcp package source.

Built for Anvia.