chore(deps): upgrade @modelcontextprotocol/server to 2.0.0 - #96
Merged
Conversation
The MCP server SDK was pinned to the 2.0.0-beta.5 pre-release. Stable 2.0.0 has since shipped, so move off the beta. No API drift: createMcpHandler and McpServer in src/lib/mcp/server.ts are unchanged, and the bundled protocol revisions stay the same (2026-07-28 current, 2025-11-25 legacy fallback).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves the MCP server SDK off a pre-release:
@modelcontextprotocol/server2.0.0-beta.5→2.0.0.Stable
2.0.0shipped (npm dist-tags: latest = 2.0.0); we were pinned to the last beta. Nothing was broken, but running a pre-release SDK against real financial data isn't ideal, and the beta→stable gap is where trailing API adjustments land.Protocol version
Unchanged — we were already current. Both beta.5 and 2.0.0 bundle the same two revisions:
2026-07-28MODERN_WIRE_REVISION)2025-11-252026-07-28is the latest published MCP spec revision. Note this is the stateless revision — no initialization handshake, no protocol-level sessions, no GET stream endpoint. The SDK's inbound legacy routing handles method rejection, soexport const GET = POSTinsrc/app/api/mcp/route.tsremains correct.No API drift
src/lib/mcp/server.tsneeded no changes —createMcpHandlerandMcpServerhave identical signatures. Diff is two files:package.jsonandpnpm-lock.yaml.Verification
Run on a clean
mainbase in an isolated worktree:pnpm install --frozen-lockfilepnpm typecheckget_dashboard_summaryreturns correct dataNote for reviewers
Integration tests were run with
--maxWorkers=4. At vitest's default concurrency the suite reports mass failures that are pure infrastructure noise — the Postgres testcontainer gets killed mid-run (57P01 ProcessInterrupts) plus a Docker 409 container-removal race. Capping workers takes the suite from 339s/137-fake-failures to 50s/green. That is a pre-existing issue, not something this PR introduces.🤖 Generated with Claude Code