ruvector/crates/ruvector-cli/src
Name cannot be blank 38105cf89b
fix(mcp): route tracing output to stderr to prevent JSON-RPC stdio corruption (#470)
The ruvector-mcp binary initializes its tracing subscriber without
specifying a writer, defaulting to stdout. Under the stdio MCP
transport this contaminates the JSON-RPC frame stream with log lines,
causing every @modelcontextprotocol/sdk client to throw a Zod parse
error on the very first frame.

Add .with_writer(std::io::stderr) to both the debug and release
tracing subscriber builders in crates/ruvector-cli/src/mcp_server.rs.

Verified by stdio smoke test: first line of stdout is now a valid
JSON-RPC initialize response with serverInfo.name == "ruvector-mcp",
and tracing output appears exclusively on stderr as required by the
MCP stdio transport spec.
2026-05-22 01:30:56 -04:00
..
cli chore: update intelligence data and version bump to v0.1.71 2025-12-31 17:40:37 +00:00
mcp fix: format all files, add EXO crate READMEs, convert path deps to version deps 2026-02-27 16:21:14 +00:00
config.rs fix(security): path traversal in MCP server vector_db_backup (CWE-22) 2026-02-25 13:32:21 +00:00
main.rs style: run cargo fmt across all crates 2025-12-29 17:41:49 +00:00
mcp_server.rs fix(mcp): route tracing output to stderr to prevent JSON-RPC stdio corruption (#470) 2026-05-22 01:30:56 -04:00