"Session" matching MCP servers:

Session Watcher treats your prompt cache as inventory — it uses EOQ theory to tell you whether the current context is still worth carrying, and when to restart. Works with any session-based coding agent.

Enables AI assistants to query and analyze past Claude Code sessions, providing structured insights like file changes, decisions, errors, and git history across projects.

Enables any MCP host to start, log, and end agent sessions and export them as a normalized, redacted timeline while keeping all data local.

MCP server that provides read-only analysis of Claude Code session transcripts, enabling queries about project activity, session details, and tool usage.

Web analytics and AI session replay for agents: visitors, breakdowns, funnels, goals, revenue attribution, and AI-found site issues. Connects to the hosted Flowsery MCP server.

A read-only MCP server that exposes local coding-agent session logs as three tools for introspection of recent work, debugging tool failures, and tracking token usage and estimated cost without parsing log files.

Enables AI assistants to search, summarize, and inspect Kibana/OpenSearch Dashboards logs through the user's logged-in browser session, eliminating the need for API keys or service accounts.

Shows what is consuming your agent context window before a session starts: always-loaded skill descriptions ranked by token cost, skills installed more than once under different names, CLAUDE.md/AGENTS.md sizes including what their @import lines pull in, and MCP servers configured across clients. Read-only: no child processes, no network.

Analyzes Telerik Fiddler SAZ session archives, enabling AI assistants to inspect, search, and filter HTTP sessions, plus performance and security auditing.

Lets AI assistants query Dynatrace Managed environments — services, traces, metrics, pods, and problems — by running read-only GET requests through your already logged-in browser session, so no API tokens are needed. All traffic stays on your machine between the AI client, a local server, and a browser extension.

Enables analyzing coding-agent session transcripts to measure tool efficiency, detect loops, track test outcomes, and report costs, with MCP tools for listing sessions, analyzing sessions, finding loops, and generating cost reports.

Streams live progress from long-running MCP tool calls to any connected client. Instrument a tool call with mcp-telemetry-sdk, and telemetry_subscribe pushes its steps, logs, cost, and completion over notifications/progress — no polling, and a job started in one session can be watched from a different one.

Enables querying PostHog with HogQL, retrieving event and property definitions, session replays, and project lists, plus optional REST API access with safeguards against accidental writes and API key leakage.

Enables search, analytics, and visualization of Claude Code sessions with MCP tools for session management, recovery, and insights.

Enables measuring the cost of completed agent workflows from runtime session logs and submitting results to the AMI survey.

Enables read-only interaction with official Embrace MCP tools while preserving full structured response data, including session aggregates and detailed logs, crashes, network, and spans, through a local stdio server.

Records every browser session (screen, DOM, network, console, storage) and enables time-travel debugging to rewind and analyze failures.

Records and rewinds AI coding agents (Claude Code, Codex, Cursor, Gemini CLI and others) locally. Its tools take a checkpoint, show the session timeline, preview and apply a rewind with a confirm code, list the tests the agent ran and whether the code changed since, write a handoff, verify the hash-chained log, and check a tool call against your guardrails.

Local-first dashboard + MCP server that parses Claude Code and Codex JSONL files into a SQLite cost / token tracker. Per-MCP and per-tool breakdown, session drill-down, dedup by request_id; never talks to vendor APIs

Enables full lifecycle management of systemd units over D-Bus, including status, start/stop/restart, unit file authoring, journal queries, timers, and system/session information.