Sessions

The Sessions tab shows every MCP session (one client connection lifecycle) with drill-down into individual events.

What is a session?

An MCP session starts when an AI client sends an initialize request and ends when the connection closes. During a session, the client discovers tools, calls them, and eventually disconnects.

Each session row shows:

Column	Description
Session	Session ID (from mcp-session-id header)
Client	AI client name + version (from clientInfo)
Started	When the session began (date + time)
Duration	How long the session lasted
Calls	Total MCP requests in this session
Errors	Failed requests (highlighted if > 0)
Status	Active (green) or Ended (gray)
Tools	Which tools were called

Session Detail

Click any session to expand it inline and see every event in chronological order:

• session_start — connection established
• initialize — MCP handshake with latency
• tools/list — tool discovery
• tools/call → get_weather — actual tool invocations with timing
• Session end

Each event shows its timestamp, type, tool name (if applicable), latency, and status.

What to look for

• Retry patterns — “create_payment failed, then succeeded 2 seconds later”
• Slow discovery — is tools/list taking longer than expected?
• Error context — which call failed, and what happened before and after?
• Session duration — long sessions might indicate stuck clients

Filters

• Search — filter by session ID, client name, or tool name
• Status — show only active or ended sessions
• Time range — adjust the window

Use cases

”A user reported the tool didn’t work”

1. Get the approximate time from the user
2. Find their session in the list (filter by client if known)
3. Expand the session to see exactly what happened
4. Identify the failed call, error message, and surrounding context

”Are clients using the new tool?”

1. Look at the Tools column across recent sessions
2. If the new tool doesn’t appear, clients haven’t discovered it yet
3. Check if tools/list responses include the new tool (go to Tools tab)

“Why do some sessions have high error rates?”

1. Sort or scan for sessions with errors > 0
2. Expand to see which calls failed
3. Check if errors correlate with a specific tool or time window