Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Streamable HTTP client hangs on a null-id JSON-RPC error in a 200 JSON response

Abierto Apto para principiantes
  • ¿Algo no está bien?
#3,639 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
75/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
api

Línea de trabajo

Comienza en src/mcp/client/streamable_http.py, en _handle_json_response, y compara después su gestión con _handle_sse_event y _handle_post_request. Añade la prueba de regresión junto a la prueba existente de null-id no-2xx en tests/client/test_notification_response.py; se considera terminado cuando un error JSON-RPC 200 con id null lanza MCPError en lugar de dejar la solicitud esperando.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug v1 v2
Initial Checks
Release line

2.x (current stable)

Description

On current main (2118f14f), when a server answers a request POST with a 200 application/json body holding a JSON-RPC error with "id": null, the streamable HTTP client never resolves the call. session.list_tools() (or any request) waits forever, or until a read timeout if one is set.

JSON-RPC 2.0 allows id: null on an error when the server could not determine the request id. Gateways and non-SDK servers can send one with status 200.

_handle_json_response in src/mcp/client/streamable_http.py forwards the parsed message unchanged. The dispatcher then drops it as a response to an unknown id (jsonrpc_dispatcher.py, "unknown/late request id").

The other two response paths in the same transport already handle this:

  • SSE (_handle_sse_event): replaces a response's id with the original request id.
  • Non-2xx JSON body (_handle_post_request): rebuilds the error under the request's id. The comment there says: "The server may have set id: null (request rejected before its id was parsed); use this request's id so correlation works."

So the same error body resolves the call over SSE or with a 4xx status, but hangs with a 200.

Expected: the call raises MCPError with the server's error, the same as the SSE and non-2xx paths.

Proposed fix: in _handle_json_response, when the parsed message is a JSONRPCError, set its id to the POST's request id. A 2xx JSON body answers exactly that POST, so nothing else can be waiting on it. That is a 4-line change plus a regression test next to the existing non-2xx null-id test in tests/client/test_notification_response.py.

I'd like to fix this and have a branch ready: https://github.com/hyeonsang010716/python-sdk/tree/fix/streamable-http-json-null-id

I found and prepared this with AI assistance. I've reviewed the change, checked the repro below fails on main and passes with the fix, and can explain it.

Example Code
import json

import anyio
import httpx2
from starlette.applications import Starlette
from starlette.requests import Request
from starlette.responses import JSONResponse, Response
from starlette.routing import Route

from mcp import ClientSession, MCPError
from mcp.client.streamable_http import streamable_http_client


async def handle_mcp(request: Request) -> Response:
    data = json.loads(await request.body())
    if data.get("method") == "initialize":
        result = {"protocolVersion": "2025-06-18", "capabilities": {}, "serverInfo": {"name": "s", "version": "1"}}
        return JSONResponse({"jsonrpc": "2.0", "id": data["id"], "result": result})
    if "id" not in data:
        return Response(status_code=202)
    # e.g. a gateway that fails before it has parsed the request id
    return JSONResponse({"jsonrpc": "2.0", "id": None, "error": {"code": -32603, "message": "upstream failed"}})


async def main() -> None:
    app = Starlette(routes=[Route("/mcp", handle_mcp, methods=["POST"])])
    async with httpx2.AsyncClient(transport=httpx2.ASGITransport(app=app)) as http:
        async with streamable_http_client("http://localhost/mcp", http_client=http) as (read, write):
            async with ClientSession(read, write) as session:
                await session.initialize()
                try:
                    with anyio.fail_after(3):
                        await session.list_tools()
                except MCPError as exc:
                    print("raised MCPError:", exc.error.message)
                except TimeoutError:
                    print("list_tools() never returned")


anyio.run(main)

Output on main:

list_tools() never returned

Output with the fix:

raised MCPError: upstream failed
Python & MCP Python SDK
Python 3.14.7
mcp main @ 2118f14f (also present in v2.3.0)
Lenguaje dominante
Python
Estrellas
24.5k
Forks
4k
Merge medio
1 d 14 h
PR fusionados (30 d)
34

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/python-sdk

Todos los issues de modelcontextprotocol/python-sdk

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.