Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QMX_MCP_HOSTNoHost/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_URLNoURL of the Ollama embedding backend, e.g. http://spark-1.local:11434.
QMX_CAPTURE_EXCLUDE_ROOTSNoComma-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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
queryB

Semantic + keyword search over the qmx knowledge base (code, docs, chats, learnings).

    Returns ranked hits with ``path``, ``start_line``/``end_line``, ``symbol``, ``score`` and a
    text snippet. Optional ``kind`` filters to ``code`` | ``doc`` | ``chat`` | ``learning`` |
    ``meeting``.
    
search_codeB

Search only code by meaning; returns file:line locations with snippets.

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.

    Each hit names its call: ``meeting`` (folder ``YYYY-MM-DD_<name>``), ``date``, ``file``
    (``transcript.txt`` | ``summary.md`` | ``notes.md`` | ``prep.md``), plus ``symbol``
    (transcript speakers + time range, or the summary section) and the snippet.
    
lessonsA

Recall distilled lessons — decisions, mistakes+corrections, how-tos learned before.

    Higher-signal than raw chat recall: ranked by relevance × importance × recency, each with
    citations. ``type`` filters ``decision`` | ``mistake`` | ``howto``. ``include_retired`` also
    returns deprecated/superseded lessons (hidden by default) with their ``deprecated_reason``
    and ``superseded_by`` breadcrumb — use it to check *why* something was retired.
    
add_learningA

Record a durable lesson so future sessions recall it. type: decision|mistake|howto.

    ``statement`` is the lesson in one crisp sentence; ``detail`` the why/correction/better-way;
    ``scope`` the repo it applies to as its git remote ``owner/repo`` (e.g. ``the-dsvolk/qmx``)
    — omit it for a global lesson. A bare repo name is mapped to the one known ``owner/repo``
    it matches, and rejected with the options if it matches none or several.
    
update_learningA

Fix an existing lesson in place — correct its wording or lower its importance.

    Prefer this over adding a near-duplicate when a lesson is merely wrong, stale in detail, or
    over-weighted; use ``deprecate_learning`` when it should stop firing altogether. Omitted
    fields are left unchanged (to *clear* one: ``qmx update-learning --clear-detail``).
    Returns the updated lesson, or ``None`` if ``learning_id`` does not exist.
    
deprecate_learningA

Soft-retire a lesson: it stops being recalled, but is kept with a breadcrumb.

    The right tool when a lesson turned out to be wrong or went stale — reversible, and
    preferable to leaving it firing at a lower weight. ``reason`` records why; ``superseded_by``
    points at the lesson that replaces it (omit when nothing does). Retired lessons are visible
    again via ``lessons(..., include_retired=True)`` and revivable with ``restore_learning``.
    
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.

    Use it when a lesson looks wrong or off-topic (e.g. a bad consolidation merge overwrote it),
    then ``revert_learning`` to put a previous version back. ``None`` if the lesson is unknown.
    
revert_learningA

Restore a lesson from its history; revision_id defaults to the latest revision.

    The current text is saved as a new revision first, so a revert can itself be reverted.
    Returns the restored lesson, or ``None`` if ``learning_id`` does not exist.
    
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.

    ``text`` is the idea in one line; ``why`` the context needed to pick it up cold (what
    prompted it, what to check). Pass ``cwd`` (your working directory) so the item is scoped
    to that repo, or ``scope`` (``owner/repo``) directly; omit both for a global item.
    ``session`` optionally records the transcript it came from. Returns the stored item;
    ``similar`` lists open items that look alike (mention them — it may be a duplicate).
    
list_parkedA

List parked items — only call when the user asks ("what did I park?", "parked items").

    Scoped to ``cwd``'s repo (or ``scope``) plus global items; with neither, every scope.
    ``status``: ``open`` (default) | ``done`` | ``dropped`` | ``closed`` | ``all``. ``query``
    ranks by meaning. ``stale_only`` keeps items untouched long enough to need a keep-or-drop
    review (each item also carries a ``stale`` flag).
    
unparkA

Close a parked item once the work is done (done) or abandoned (dropped).

    ``note`` records the resolution (what was done, or why it was dropped). The item is
    archived, not deleted — ``qmx reopen <id>`` brings it back.
    
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 chunk_id (from a prior result).

statusB

Index stats (documents/chunks/mentions) and Ollama backend health.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 17 tools

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues