mcp-copilotcli-history
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_sessionsA | Search through all Copilot session history for a pattern. This tool searches across all stored Copilot conversations to find messages, tool calls, and other events matching your query. Use this to find past discussions, code snippets, or decisions. Args: query: The search term or regex pattern to find event_type: Optional filter for event type (user.message, assistant.message, tool.result) max_results: Maximum number of results to return (default: 20) case_sensitive: Whether to perform case-sensitive matching (default: False) Returns: List of matching entries with session context and content snippets |
| list_recent_sessionsA | List the most recent Copilot sessions with their titles. Use this to get an overview of recent conversations and find sessions to explore further. Args: limit: Maximum number of sessions to return (default: 10) Returns: List of recent sessions with metadata (id, title, date, model, size) |
| get_session_statsB | Get statistics about all Copilot session history. Returns aggregate information about stored sessions including total count, size, date range, event types, and models used. Returns: Dictionary with session statistics |
| get_session_conversationA | Get the conversation from a specific session. Retrieves the user and assistant messages from a session in chronological order, allowing you to review a past conversation. Args: session_id: The session ID (full or partial) to retrieve include_tool_calls: Whether to include tool call details (default: False) max_messages: Maximum number of messages to return (default: 50) Returns: List of messages from the session in chronological order |
| search_by_file_pathA | Find sessions that referenced a specific file or path pattern. Searches through session history for mentions of file paths, useful for finding past work on specific files or directories. Args: file_pattern: File path or pattern to search for (e.g., "main.py", "src/") max_results: Maximum number of results to return (default: 20) Returns: List of sessions and entries that referenced the file pattern |
| search_tool_usageA | Find sessions where specific tools were used. Search for tool invocations in past sessions, optionally filtered by tool name. Useful for finding examples of how tools were used. Args: tool_name: Optional tool name to filter by (e.g., "create_file", "run_in_terminal") max_results: Maximum number of results to return (default: 20) Returns: List of tool usage instances with context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of session history: retrieval, statistics, listing, and various search types (by file path, full-text, tool usage). There is no overlap in functionality.
All tools use snake_case with a consistent verb_noun pattern (e.g., get_session_conversation, search_by_file_path). The naming is predictable and intuitive.
6 tools is an ideal size for a focused history server. It covers all core operations without being overwhelming or insufficient.
The tool set covers browsing, listing, and searching sessions comprehensively. Minor gaps exist: there is no tool to delete or export session history, which might be expected for a history management utility.