mcp-session-insight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsC | List all sessions, optionally filtered by project |
| show_sessionA | Show metadata for a session (project, time, message count). Use this for a quick overview. For full content, use get_session_conversation or get_session_summary. |
| search_sessionsC | Search sessions by keyword |
| get_session_summaryA | Get a comprehensive summary for a session. Returns structured JSON data (EnrichedSummary). Based on this data, synthesize a concise Chinese summary for the user covering: what was done, key files changed, errors encountered, and decisions made. This is the SINGLE tool to call when the user wants to understand what happened in a session. Do NOT call other tools after this. |
| get_session_changesA | Get file changes (created/modified) for a session. Only call this if the user explicitly asks for file changes. |
| get_session_requestsA | Get deduplicated user requests for a session. Only call this if the user explicitly asks for user requests. |
| get_session_todosA | Get todo snapshots for a session. Only call this if the user explicitly asks for todo progress. |
| get_session_errorsA | Get errors/issues for a session. Only call this if the user explicitly asks for errors. |
| get_session_decisionsA | Get decisions for a session. Only call this if the user explicitly asks for decisions. |
| get_session_conversationB | Get conversation messages for a session |
| get_git_logsA | Collect git commit logs across projects. Returns structured JSON grouped by project. Only call this if the user explicitly asks for git logs or commit history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| session_handoff | Generate a handoff context prompt for a session |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Sessions | JSON array of all sessions |
TDQS
Scored across 11 tools
Each tool targets a distinct aspect of sessions (git logs, changes, conversation, decisions, errors, requests, summary, todos, listing, searching, metadata). Descriptions include explicit guidance on when to use each, preventing confusion.
All tools follow a consistent verb_noun pattern (e.g., get_git_logs, get_session_changes, list_sessions) using snake_case, with no deviations or mixed conventions.
With 11 tools, the server thoroughly covers session insight without redundancy. Each tool serves a unique query, fitting the scope well.
The tool set covers all common retrieval needs for session analysis (metadata, conversation, changes, errors, decisions, etc.), with no obvious gaps for a read-only insight server.