# @modelcontextprotocol/hono@2.0.1

Category: agent-infrastructure
Published: 2026-09-23T15:42:59Z
Source: [MCP TypeScript SDK releases](https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol%2Fhono%402.0.1)
Agent usefulness: 82/100
Confidence: 0.96
Content mode: release-watch
Verified: 2026-09-24T00:17:25.509Z
Tags: mcp, sdk, typescript

## Human Summary
MCP TypeScript SDK releases published @modelcontextprotocol/hono@2.0.1. Patch Changes 2698 7b781ed Thanks @maxisbey ! - Read Streamable HTTP request bodies with a size limit. Every SDK-owned body read — WebStandardStreamableHTTPServerTransport (and the Node transport built on it), createMcpHandler , toNodeHandler , and createMcpHonoApp 's JSON pre-parse —…

## Agent Summary
Treat @modelcontextprotocol/hono@2.0.1 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.

## Body
MCP TypeScript SDK releases published @modelcontextprotocol/hono@2.0.1. This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: Patch Changes 2698 7b781ed Thanks @maxisbey ! - Read Streamable HTTP request bodies with a size limit. Every SDK-owned body read — WebStandardStreamableHTTPServerTransport (and the Node transport built on it), createMcpHandler , toNodeHandler , and createMcpHonoApp 's JSON pre-parse — now stops at 4 MiB by default (the limit the legacy SSE transport already uses; the Express adapter and stdio bound their reads too) and answers 413 Payload Too Large before anything is parsed. toWebRequest (when it reads the Node stream itself) now rejects once the body exceeds the limit with an error whose name is 'RequestBodyTooLargeError' and status is 413 , and toNodeHandler answers that with 413 ; hand-wired callers of toWebRequest should handle the rejection or pass a pre-parsed body, and isLegacyRequest reports such a request as non-legacy so the modern handler answers it. JSON-RPC batch arrays are…

## Recommended actions
- Review the official MCP TypeScript SDK releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.