Unified History MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFIED_HISTORY_CONFIG | No | Path to the TOML configuration file. Defaults to ~/.config/unified-history-mcp/config.toml or ./unified-history.toml. |
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 |
|---|---|
| searchA | Search across domains with FST-backed full-text search. Domains: sessions — Vibe coding session conversations transcripts — Meeting transcripts (supports speaker filter) notifications — Teams notification logs all — Search across all three domains at once (default) Args: domain: Domain to search, or "all" for cross-domain (default: all) query: Search text (or regex pattern if regex=True) max_results: Maximum total matches to return (default 20) date_from: Optional start of date range (YYYY-MM-DD) date_to: Optional end of date range (YYYY-MM-DD, inclusive) regex: If True, treat query as a regex pattern context_lines: Lines of surrounding context per match (default 2) case_sensitive: If True, match case-sensitively (default False) max_matches_per_file: Max matches from any single file (default 5) role: [sessions] Filter by role: user, assistant, tool speaker: [transcripts] Filter by speaker name |
| list_domainA | List available files in a domain with metadata and summaries. Args: domain: Domain to list (sessions, transcripts, notifications) date_from: Optional start of date range (YYYY-MM-DD) date_to: Optional end of date range (YYYY-MM-DD, inclusive) max_results: Maximum entries to show (default 50) |
| readB | Read entries from a domain file. Args: domain: Domain (sessions, transcripts, notifications) id: File/directory name or unique prefix max_entries: Maximum entries to return, newest first (default 50) role: [sessions] Filter by role: user, assistant, tool speaker: [transcripts] Filter by speaker name |
| summaryA | Get the AI-generated summary for a domain entry. Args: domain: Domain (sessions, transcripts) id: File/directory name or unique prefix |
| rebuildA | Rebuild FST indexes for configured domains. Args: domain: Domain to rebuild, or "all" for all configured domains |
| search_historyA | Search the Vibe command history (vibehistory file). Args: query: Search text (or regex pattern if regex=True) max_results: Maximum matches to return (default 30) regex: If True, treat query as a regex pattern case_sensitive: If True, match case-sensitively (default False) |
| search_logA | Search the Vibe runtime log (vibe.log). Args: query: Search text (or regex pattern if regex=True) max_results: Maximum matches to return (default 30) regex: If True, treat query as a regex pattern case_sensitive: If True, match case-sensitively (default False) level: Filter by log level: WARNING, INFO, ERROR, DEBUG |
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 7 tools
Most tools are clearly distinct: list_domain enumerates files, read retrieves entries, summary provides AI-generated overviews, and rebuild manages indexes. The three search-related tools (search, search_history, search_log) could cause some confusion, but their descriptions clearly separate domain search from specific-file searches.
Naming conventions are mixed: some tools use single verbs (search, read, summary, rebuild) while others use verb_noun patterns (list_domain, search_history, search_log). 'summary' is a noun rather than an imperative verb, breaking the expected pattern. Overall, the names are readable but not uniformly styled.
With 7 tools, the server is well-scoped for its purpose of providing unified search and read access to historical data. Each tool serves a distinct function without unnecessary bloat, and the count is appropriate for the domain.
The tool set covers the core lifecycle for a read-only history server: searching, listing, reading, and summarizing entries, plus index maintenance. The only notable gap is that the summary tool does not support the notifications domain, and there is no explicit tool for configuring domains (though rebuild handles index updates).