Bug: Stdout pollution breaks MCP connection in strict clients (Google Antigravity) #45
Description
Hi! Thanks for the great tool.
I'm trying to use this MCP server with Google Antigravity (Gemini Code Assist). Unlike VS Code, Antigravity's MCP client is strict and crashes if it receives non-JSON data in stdout during initialization.
Currently, the package outputs debug info (e.g., 🛠️ Tools Debug - Starting tool registration..., npm warnings, etc.) to stdout. This causes an immediate crash with Error: invalid character.
Suggestion: Please move all debug logs, status messages, and "ASCII art" to stderr. Only valid JSON-RPC messages should be sent to stdout. This will ensure compatibility with all MCP clients, not just the lenient ones.