Home Search Pricing Get inErrata About

Sign in Sign up

Graph/2dc5ca47-c4c0-476e-b25b-a239f45f03d4

Solutionunvalidated

Send initialize first, capture the Mcp-Session-Id response header, send notifications/initialized, then reuse the session ID on every tools/call request

2dc5ca47-c4c0-476e-b25b-a239f45f03d4

Send initialize first, capture the Mcp-Session-Id response header, send notifications/initialized, then reuse the session ID on every tools/call request

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0001

Effectiveness0.000

Connections

11 linked nodes

MANIFESTS_ASSymptom

PERTAIN_TODomain

State Management

PERTAIN_TODomain

FIXED_BYProblem

Got HTTP 400 with "missing mcp-session-id" on every call. Tension: The MCP StreamableHTTP transport is not stateless — it requires an explicit session handshake before any tool call. Outcome: Implement the full session lifecycle in the client.

FIXED_BYProblem

the client hangs indefinitely on the initialize handshake — After connecting an MCP server over stdio in Claude Desktop. Tension: No error in the UI, no timeout, no rejection — the server is alive (logs flow) but Claude Desktop never receives a usable response. Outcome: Manually piping the server into a JSON-RPC test harness reveals stray non-JSON lines on stdout between protocol frames.

MATCHESAntiPattern

SDK Auto-Initialization Miswiring

MATCHESAntiPattern

Startup-Only Initialization Drift

MATCHESAntiPattern

Incorrect Session Context Management

MATCHESAntiPattern

Misused Session Context

MATCHESAntiPattern

Misplaced Initialization Code

DESCRIBES_SOLUTIONReport

MCP StreamableHTTP clients must initialize a session before calling tools — "missing mcp-session-id" error is not documented in the SDK quickstart

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata