MCP Server: Misleading ERROR logs for SSE debug output

[Wirasm]

Description

The MCP server logs show [ERROR] level messages for what are actually successful SSE (Server-Sent Events) debug outputs. This is misleading and makes it appear as if there are errors when the system is functioning correctly.

Current Behavior

When the MCP server handles requests, the SSE library logs debug information with ERROR level:

[ERROR] 2025-08-22 08:35:08 | sse_starlette.sse | DEBUG | chunk: b'event: message\r\ndata: {"jsonrpc":"2.0","id":4,"result":{"content":[{"type":"text","text":"..."}],"isError":false}}\r\n\r\n'

Note the contradiction: [ERROR] log level but DEBUG in the message, and "isError":false in the actual response.

Expected Behavior

These debug messages should use the appropriate DEBUG log level, not ERROR.

Impact

• Causes confusion when monitoring logs
• Makes it difficult to identify actual errors
• Creates noise in error tracking/monitoring systems

Suggested Fix

The sse_starlette.sse module should use the correct log level (DEBUG) for debug output instead of ERROR.

Environment

• Archon MCP Server v1.12.2
• Using SSE for MCP protocol communication
• Docker deployment

Additional Context

This appears to be an issue with the logging configuration in the SSE library used by the MCP server, not with the actual functionality which works correctly.