[Bug for MCP&API]: Windows MCP server JSON parsing error

[liaoyangr8-ai]

Basic Information - Models Used

mcp foe openclaw

Basic Information - Scenario Description

PS C:\Users\Admin> uvx minimax-coding-plan-mcp Starting Minimax MCP server [02/09/26 18:55:00] ERROR Received exception from stream: 1 validation error for server.py:700 JSONRPCMessage Invalid JSON: EOF while parsing a value at line 2 column 0 [type=json_invalid, input_value='\n', input_type=str] For further information visit https://errors.pydantic.dev/2.12/v/json_invalid {"method":"notifications/message","params":{"level":"error","logger":"mcp.server.exception_handler","data":"Internal Server Error"},"jsonrpc":"2.0"}

Is this bug known and solvable?

• I have followed the GitHub READMEs for Minimax-MCP and Minimax-MCP-JS.
• I have checked the official Minimax documentation and existing GitHub issues，but found no solution.

Information about environment

PS C:\Users\Admin> uvx minimax-coding-plan-mcp
Starting Minimax MCP server

[02/09/26 18:55:00] ERROR Received exception from stream: 1 validation error for server.py:700
JSONRPCMessage
Invalid JSON: EOF while parsing a value at line 2
column 0 [type=json_invalid, input_value='\n',
input_type=str]
For further information visit
https://errors.pydantic.dev/2.12/v/json_invalid
{"method":"notifications/message","params":{"level":"error","logger":"mcp.server.exception_handler","data":"Internal Server Error"},"jsonrpc":"2.0"}

Trace-ID in the request head

PS C:\Users\Admin> uvx minimax-coding-plan-mcp Starting Minimax MCP server [02/09/26 18:55:00] ERROR Received exception from stream: 1 validation error for server.py:700 JSONRPCMessage Invalid JSON: EOF while parsing a value at line 2 column 0 [type=json_invalid, input_value='\n', input_type=str] For further information visit https://errors.pydantic.dev/2.12/v/json_invalid {"method":"notifications/message","params":{"level":"error","logger":"mcp.server.exception_handler","data":"Internal Server Error"},"jsonrpc":"2.0"}

Description

Steps to reproduce

This happens to Minimax_M1 and xxx.
The bug can be reproduced with the following steps:

1. ...
2. ...

The following example input & output can be used:

system: ...
user: ...
...

Expected results

The results are expected to be ...

Actual behaviours

The actual outputs are as follows: ...

Error logs

The error logs are as follows: ...

The screenshots are as belows: