Inspect a workspace through MCP

Edit this page on GitHub

LibTmux.Workspace 0.0.0-alpha.14 · Source

Inspect the session you loaded with the .NET workspace CLI by pointing its MCP server at the same tmux socket. The loaded windows and panes are ordinary tmux objects; discovery returns their existing IDs.

This guide uses development workspace-cli source. Continue the installation walkthrough through its detached load, keeping that shell and WORKSPACE_TMP available. Leave the workspace-guide session running. Build both executables from the same native repository checkout; released package instructions may describe different MCP contracts.

Build the MCP serverLink to section

Run from the native repository root with the installation walkthrough’s toolchain and dependencies.

$ dotnet build \
    --configuration Release \
    --framework net10.0 \
    -m:2 \
    src/LibTmux.Mcp/LibTmux.Mcp.csproj

Use the repository’s SDK and a compatible .NET 10 runtime. Keep the complete build output beside the DLL, including its runtime and dependency metadata.

Select the same socketLink to section

Configure an MCP client to launch the following command with the shown environment. The client owns the process’s standard input and output for JSON-RPC messages.

$ LIBTMUX_TOOLSETS=inspect \
    LIBTMUX_SOCKET_PATH="$WORKSPACE_TMP/tmux.sock" \
    dotnet src/LibTmux.Mcp/bin/Release/net10.0/LibTmux.Mcp.dll

In a client’s configuration file, use absolute executable or script paths and expand WORKSPACE_TMP to its actual value. Configuration files do not perform shell variable expansion. Retain the environment used to build and run the native executable.

For a workspace loaded with -L NAME, set LIBTMUX_SOCKET=NAME instead of LIBTMUX_SOCKET_PATH. Do not set both. If you selected a tmux executable with LIBTMUX_TMUX, supply that same setting to the MCP process.

Inspect and waitLink to section

1. Discover tools with tools/list and read the tmux://capabilities resource. Confirm that its resolved endpoint matches the loaded socket.
2. Call list_sessions, then list_windows with session: "workspace-guide", and list_panes. Retain the returned session, window and pane IDs.
3. Select one returned pane ID for capture or a bounded text wait. Use the argument names below; discover the full schema before adding options.

Set "timeoutSeconds" to 10 for a ten-second wait. A pending wait permits other inspection calls on the same connection. To check that behavior, start a wait for text absent from the pane, then request list_panes before its deadline. Client cancellation uses notifications/cancelled with the outstanding request ID; the connection remains usable for inspection.

Capture returns a bounded "lines" array inside "content" with trailing empty rows removed; interior blank lines remain. snapshot_pane adds cursor and viewport state. The first capture_since call establishes an opaque cursor without returning content; pass that cursor to subsequent calls.

If discovery does not show workspace-guide, compare the resolved socket in capabilities with the CLI’s -S path. A different socket selects a different daemon even when session names match.

Close the connectionLink to section

Close the MCP connection’s standard input to stop the server and release pending work. This separately loaded workspace remains running. When you finish the walkthrough, remove only its session on the same socket:

$ tmux \
    -S "$WORKSPACE_TMP/tmux.sock" \
    kill-session \
    -t '=workspace-guide'

The configuration remains in the temporary directory until you remove it.

See the verified native workspace workflow and development MCP reference for this source contract. The site’s released MCP pages retain their version-pinned contracts.