qmx
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QMX_MCP_HOST | No | Host/interface for the qmx MCP HTTP server. Defaults to 127.0.0.1; set to 0.0.0.0 to bind on the LAN. | |
| QMX_OLLAMA_URL | No | URL of the Ollama embedding backend, e.g. http://spark-1.local:11434. | |
| QMX_CAPTURE_EXCLUDE_ROOTS | No | Comma-separated list of workspace folders whose sessions qmx capture and qmx session-end should ignore. |
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 |
|---|---|
| queryB | Semantic + keyword search over the qmx knowledge base (code, docs, chats, learnings). |
| search_codeB | Search only code by meaning; returns |
| recallB | Recall past Claude Code conversations — semantic search over indexed chat turns. Returns matching turns with their transcript path, line, and role (user/assistant). |
| meetingsB | Search recorded meetings (Memoir calls) — transcripts, summaries, notes and prep. |
| lessonsA | Recall distilled lessons — decisions, mistakes+corrections, how-tos learned before. |
| add_learningA | Record a durable lesson so future sessions recall it. |
| update_learningA | Fix an existing lesson in place — correct its wording or lower its |
| deprecate_learningA | Soft-retire a lesson: it stops being recalled, but is kept with a breadcrumb. |
| restore_learningA | Un-retire a lesson deprecated by mistake — clears the retire/supersede markers. |
| learning_historyA | A lesson's earlier versions, newest first — every in-place update keeps the old text. |
| revert_learningA | Restore a lesson from its history; |
| parkA | Park an idea to come back to later — when the user says "park this", "remind me later", "let's come back to that", or mid-task surfaces a side idea not worth derailing for. |
| list_parkedA | List parked items — only call when the user asks ("what did I park?", "parked items"). |
| unparkA | Close a parked item once the work is done ( |
| resume_parkedB | Pick a parked item back up: the item plus the past chat turns that best match it, so the original context is restored, not just the one-line note. |
| getA | Fetch a single chunk's full text + location by |
| statusB | Index stats (documents/chunks/mentions) and Ollama backend health. |
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 17 tools
The learning lifecycle tools (add/update/deprecate/restore/history/revert) and the parking tools (park/list_parked/unpark/resume_parked) are cleanly separated by distinct verbs. The main overlap is that `query` is a superset covering code, chats, meetings and lessons, so `search_code`, `recall`, `meetings` and `lessons` can look redundant against it, and `lessons(include_retired=True)` versus `learning_history` needs the descriptions to disambiguate. Descriptions do carry enough signal to pick correctly in practice.
Most learning and parking tools follow a clean verb_noun pattern (add_learning, deprecate_learning, list_parked, resume_parked), but the retrieval tools break it with bare nouns and vague verbs (query, recall, lessons, meetings, get, status). `search_code` mixes noun-then-verb, adding a second convention to the set. Still readable, but not a single predictable pattern.
17 tools is at the upper edge of comfortable but each one maps to a real operation; the seven-tool learning lifecycle is granular yet all roles are distinct. The surface is scoped to three coherent areas (search/retrieval, learnings, parking) rather than sprawling. Slightly heavy but nothing feels gratuitous.
Learnings have full lifecycle coverage (create, update, deprecate, restore, history, revert) and parking has create/list/resolve/resume, plus retrieval has `get` and `status` to close the loop on results. Minor gaps: archived parked items can only be reopened via the CLI (`qmx reopen`, referenced but not exposed as a tool), and there is no tool to index new content, only to search it.