mcp(resources): Add socket_name support to resource handlers

[tony]

Context

All 6 resource handlers in src/libtmux/mcp/resources/hierarchy.py call _get_server() with no arguments, while every tool function accepts socket_name: str | None = None. The server instructions at server.py:20 promise multi-server support via socket_name, creating a capability gap between tools and resources.

Problem

Resources always connect to the default socket (or LIBTMUX_SOCKET env var). There's no way to read resources from alternate tmux sockets.

Proposed Solution

Investigate whether FastMCP resource URI templates can accept query parameters (e.g., tmux://sessions?socket=foo) or if a separate approach is needed. This may require upstream FastMCP changes.

Files

• src/libtmux/mcp/resources/hierarchy.py — all 6 resource handlers

[tony]

Fixed in commit b47634b — added {?socket_name} RFC 6570 query param to all 6 resource URI templates.