Extract Client and Server Information from Initialize Request

[naji247]

Overview

There's a TODO comment in the codebase indicating that client and server information should be extracted from the initialize request but this functionality is not yet implemented. This information is valuable for analytics and debugging.

Current State

In src/mcpcat/modules/overrides/mcp_server.py, the wrapped_initialize_handler has a TODO comment indicating this feature is missing. The initialize request contains valuable metadata about both the client and server that should be captured.

Requirements

When an MCP server receives an initialize request, we should extract and store:

Client Information:

• Client name and version
• Client capabilities
• Protocol version

Server Information:

• Server name and version
• Server capabilities
• Supported features

Why This Matters

• Helps track which clients are using MCP servers
• Enables version compatibility monitoring
• Provides insights into feature adoption
• Assists in debugging client-server issues
• Improves analytics dashboard usefulness

Acceptance Criteria

• Client info is extracted from InitializeRequest and stored
• Server info is captured from InitializeResult response
• Information is included in the initialization event
• Data persists across the session
• Handles missing fields gracefully
• Updates existing tests to verify the extraction

Getting Started

1. Look at the InitializeRequest and InitializeResult types in MCP SDK
2. Find the wrapped_initialize_handler in mcp_server.py
3. Review how session_info is currently managed
4. Check how other fields are extracted and stored
5. Follow the existing event structure patterns

Notes

• Ensure backward compatibility with servers that don't provide all fields
• Consider privacy implications of storing client information
• Make sure the implementation doesn't break existing functionality