magpie-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGPIE_SEARCH_HOME | No | Data directory (DB, models, logs) | ~/.magpie-search |
| MAGPIE_SEARCH_AUDIT_LOG | No | Per-call audit log | $MAGPIE_SEARCH_HOME/llm-audit.jsonl |
| MAGPIE_SEARCH_TELEMETRY | No | Set to 1 to enable telemetry (opt-in) | |
| MAGPIE_SEARCH_TOKENIZER | No | Set to `tiktoken` for precise budget counting | heuristic |
| MAGPIE_SEARCH_MODELS_DIR | No | fastembed model cache | $MAGPIE_SEARCH_HOME/models |
| MAGPIE_SEARCH_OLLAMA_HOST | No | Ollama server URL | http://localhost:11434 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search indexed Claude Code transcripts. Returns top-k matching message snippets. Results are leads to verify, never authoritative fact. Pass 'sources' to fan out across multiple backends (e.g. transcripts + files + plugins): results are then tagged with source + trust tier and trimmed to a token budget. |
| recentA | Return the most-recent messages across the index, newest first. Use this to catch up on the latest activity ("what was discussed most recently?") without a search query. To read one specific known session in order, prefer the 'session' tool instead. Optionally narrow to a single session or project. Read-only; each row includes its text, session id, and timestamp. |
| sessionA | Read one full conversation in chronological order, oldest message first, a page at a time. Use after you already have a session_id (from 'list_sessions' or a 'search' hit) and want to read that whole session in order rather than search across many. Page through long sessions with limit/offset. Read-only. |
| list_sessionsA | List the most-recent Claude Code sessions (conversations) in the index, newest first. This is the browse/discovery entry point: use it to find out what sessions exist and get their session_id values before calling 'session' (read one in full) or 'recent' (latest messages). Prefer 'search' when you are looking for specific content rather than browsing. Returns one row per session — session_id, project, message count, and last-activity time. Read-only; never modifies the index. |
| statsA | Index health summary (message/session counts, coverage). |
| reindexA | Run one incremental indexing pass so search is fresh. Local-only; reads ~/.claude/projects transcripts. |
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 operation: listing sessions, recent messages, reindexing, searching, reading a full session, and stats. Descriptions clearly differentiate them, minimizing confusion.
Names include verb_noun (list_sessions), verbs (search, reindex), nouns (session, stats), and an adjective (recent). No consistent pattern, but they are short and intuitive.
6 tools cover the essential operations for browsing, searching, and reading sessions without being excessive. Well-scoped for the server's purpose.
The set covers session discovery (list_sessions, recent), content retrieval (search, session), maintenance (reindex), and health checks (stats). No obvious gaps for a read-only session browser.