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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xfloukiex-lab/magpie-search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server