Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Context Mem is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Memory + context infrastructure for AI agents. LLM Wiki auto-sync, 15 content-aware summarizers, hybrid search (BM25 + vector + optional LLM judge), entity intelligence, decision trails, Obsidian plugin. Fully local, zero cost. MIT.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user context-mem-mcp '--' npx -y context-mem
# 2 — ask your agent for something these tools do
# agent_register, agent_status, claim_files and 41 more
Context Mem costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Context Mem as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user context-mem-mcp '--' npx -y context-memReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
44 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Register the current session as a named agent for multi-agent coordination.
No parameter schema on file.
List all active agents with their tasks and claimed files.
No parameter schema on file.
Claim files for the current agent. Returns conflicts if already claimed by another agent.
No parameter schema on file.
Broadcast a message to all active agents via the event system.
No parameter schema on file.
Store a new observation (content snippet) into context memory with automatic summarization.
No parameter schema on file.
Summarize a piece of content using the matching summarizer plugin without storing it.
No parameter schema on file.
Retrieve observations in reverse-chronological order with optional filters.
No parameter schema on file.
Retrieve a single observation by its ID.
No parameter schema on file.
Get token economy statistics for the current session.
No parameter schema on file.
Update a mutable configuration key at runtime.
No parameter schema on file.
Query the knowledge graph. Find entities and their relationships.
No parameter schema on file.
Add a relationship between two entities in the knowledge graph. Creates entities if they do not exist.
No parameter schema on file.
Find all entities connected to a given entity. Faster than graph_query for simple lookups.
No parameter schema on file.
Extract entities (technologies, people, files, components) from text content.
No parameter schema on file.
List all detected person entities with relationship counts.
No parameter schema on file.
Save a knowledge entry with automatic contradiction detection. When contradictions are found, the save is blocked — resubmit with force: true to save anyway.
No parameter schema on file.
Promote a project knowledge entry to the global cross-project knowledge store. Privacy engine sanitizes content before storing.
No parameter schema on file.
Search the global cross-project knowledge store.
No parameter schema on file.
View pending merge suggestions for duplicate global knowledge entries.
No parameter schema on file.
Resolve a contradiction between knowledge entries by merging, superseding, or keeping both.
No parameter schema on file.
Query knowledge that was valid at a specific point in time. Returns facts that were active at the given timestamp.
No parameter schema on file.
Generate a human-readable narrative from session data. Formats: pr (pull request), standup, adr (architecture decision record), onboarding.
No parameter schema on file.
Reconstruct the evidence chain behind a code change or decision. Returns the trail of events that led to a decision.
No parameter schema on file.
Predict which memory entries are at highest risk of being forgotten or archived. Users can pin important entries to protect them.
No parameter schema on file.
Generate a scored session primer with 4-layer context: project profile, critical knowledge, recent decisions, and top entities.
No parameter schema on file.
[v4] Unified search across observations, knowledge, content, topics. Legacy search/search_knowledge/search_content/recall/browse/global_search/ask are aliased to this with deprecation _meta.
No parameter schema on file.
Index content into the content store with code-aware chunking for later search.
No parameter schema on file.
Search the content store for indexed content chunks.
No parameter schema on file.
Search the knowledge base using 3-layer search (FTS5 → trigram → scan). Optionally include global cross-project knowledge. By default only returns currently-valid facts (valid_to IS NULL).
No parameter schema on file.
Verbatim memory retrieval with importance filtering and rich attribution. Returns original content, not summaries.
No parameter schema on file.
Ask a natural language question about the project. Searches knowledge, observations, events, and graph entities.
No parameter schema on file.
Browse observations by topic, person, or time dimension.
No parameter schema on file.
Update the project quick profile — a 3-5 line summary shown at every session start. Auto-generates from knowledge if no content provided.
No parameter schema on file.
Get current budget usage and status for the session.
No parameter schema on file.
Configure budget settings (session limit, overflow strategy).
No parameter schema on file.
Restore a previous session snapshot by session ID.
No parameter schema on file.
Emit a context event with priority and metadata.
No parameter schema on file.
Query context events with optional filters.
No parameter schema on file.
View or compare the project state at any point in time. Shows observations, knowledge, and events as of a target date.
No parameter schema on file.
Import external conversation exports (Claude, ChatGPT, Slack, plaintext) into context memory.
No parameter schema on file.
List all detected topics with observation counts.
No parameter schema on file.
Find topics that appear in 2+ projects (cross-project knowledge bridges).
No parameter schema on file.
Query internal error log. Shows what context-mem subsystems have failed at (embedder, entity extraction, topic storage, dreamer, etc.). Useful for doctor-style debugging.
No parameter schema on file.
Generate session handoff — saves state and returns continuation prompt for a new session. Use when context is running low or before ending a session.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Context Mem or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 4.0.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Context Mem can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.