You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Are there plans to migrate LibreChat from @modelcontextprotocol/sdk v1.x to the new v2 packages and support the MCP 2026-07-28 protocol revision?
I noticed that PR #14820 intentionally updated LibreChat to @modelcontextprotocol/sdk 1.30.0 and mentioned that the upstream active line is now the 2.0.0 scoped packages.
I'm specifically interested in SEP-2243 support. Some MCP servers now expose tool parameters using x-mcp-header and expect the MCP client to mirror those arguments as Mcp-Param-* HTTP headers.
For example:
This behavior is implemented by the MCP TypeScript SDK v2 for 2026-07-28, but LibreChat currently appears to remain on @modelcontextprotocol/sdk ^1.30.0.
Is migration to SDK v2 / MCP 2026-07-28 currently planned or being tracked somewhere?
If not, would a feature request for 2026-07-28 support be useful?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Are there plans to migrate LibreChat from
@modelcontextprotocol/sdkv1.x to the new v2 packages and support the MCP2026-07-28protocol revision?I noticed that PR #14820 intentionally updated LibreChat to
@modelcontextprotocol/sdk 1.30.0and mentioned that the upstream active line is now the 2.0.0 scoped packages.I'm specifically interested in SEP-2243 support. Some MCP servers now expose tool parameters using
x-mcp-headerand expect the MCP client to mirror those arguments asMcp-Param-*HTTP headers.For example:
requires:
This behavior is implemented by the MCP TypeScript SDK v2 for
2026-07-28, but LibreChat currently appears to remain on@modelcontextprotocol/sdk ^1.30.0.Is migration to SDK v2 / MCP
2026-07-28currently planned or being tracked somewhere?If not, would a feature request for
2026-07-28support be useful?All reactions