# @contextq/mcp

MCP server for ContextQ — exposes the full ContextQ knowledge-management API as Model Context Protocol tools

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.1.1
- **Author:** Unknown
- **License:** MIT
- **npm:** @contextq/mcp
- **Endpoints:** streamable-http https://app.contextq.dev/mcp
- **Source:** https://github.com/contextq/contextq-mcp
- **Endpoint health:** reachable (last checked 2026-10-11T15:37:21.963Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-11T20:13:42.028Z
- **Version scanned:** 2.1.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `ctx_save`
- `ctx_search` — Search / recall saved knowledge and memories using hybrid full-text + semantic search ranked by relevance — the default tool for 'what do I know about X' or 'di
- `ctx_explain_recall`
- `ctx_list` — List context entries with optional filters. Use this to browse existing contexts by workspace, project, type, or tag without a search query.
- `ctx_get` — Get a single context entry by its ID. Use this when you already know the exact context ID you want to read. Response includes lifecycle, atomic, quality_score, 
- `ctx_update` — Update an existing context entry. Only the provided fields are changed; omitted fields remain unchanged. Use this to correct, append to, reclassify, or retire (
- `ctx_delete` — Permanently delete a context entry by ID. This action cannot be undone. Use this only when you are sure the entry should be removed.
- `ctx_bulk_update` — Apply the same lifecycle move and/or archive flag to many contexts in a single call. Use this when you need to retire, mature, or reclassify a batch (capped at 
- `ctx_undo_archive` — Undo a memory-evolution auto-archive within the configurable window (default 72h, env EVOLUTION_ARCHIVE_UNDO_WINDOW_HOURS). Only contexts archived by the memory
- `ctx_undo_archive_info` — Check whether a context's auto-archive is still undo-able. Returns `{eligible: bool, archivedAt, expiresAt, archivedByFocalId, confidence, withinWindow}`. Use b
- `ctx_import` — Bulk import context entries from an external source. Optionally filter by workspace and preview with a dry run before committing.
- `ctx_stats` — Get aggregate statistics: total context count, breakdown by workspace, type, tag, recently updated entries, and orphan_rate (notes with no tags and no inbound r
- `ctx_dream`
- `ctx_link` — Manually create a typed link from one context to another (supersedes/contradicts/implements/derived_from/related_to). The backend already auto-creates links dur
- `ctx_links` — List typed links for a context — incoming, outgoing, or both. Use this to discover how a context is connected (what it supersedes, what supersedes it, what impl
- `ctx_evolve` — Re-run memory evolution for an existing context. Examines K=5 nearest neighbors and creates typed links / archives superseded notes via LLM judging. Use when yo
- `ctx_chunks` — List the block-level chunks for a context, ordered by chunk_index. Each chunk includes its heading_path, content, and has_embedding flag (false while the embedd
- `ctx_code_refs` — Find every file that imports or calls a given source file. Returns the set of referencing files (with link type and callee-symbol hint) from the code graph stor
- `ctx_code_trace` — Trace the directional call chain FROM a given source file via BFS over CALLS edges in the code graph. Returns nodes and edges so you can reconstruct the call pa
- `ctx_provenance_get`
- `ctx_confidence_get`
- `ctx_belief_history`
- `ctx_blast_radius`
- `ctx_graph_search`
- `ctx_entity_get` — Fetch an entity card from the knowledge graph: the entity's identity (name, aliases, type, summary), its current edges (facts currently believed true), and its 
- `ctx_mocs` — List Maps of Content (MOCs) for the tenant. MOCs are curated index notes that summarize and link to clusters of related contexts, providing a navigation layer o
- `ctx_regenerate_mocs` — Regenerate Maps of Content by re-clustering the tenant's contexts and synthesizing one MOC per cluster via LLM. Expensive (runs an LLM call per cluster) — call 
- `ctx_maps` — List memory maps (Dream-generated multi-shape navigation TOCs) for the caller's tenant. Optionally filter by workspace / project slug. Each row carries `{id, sh
- `ctx_saved_searches_list` — List all saved searches visible to the caller (their own + tenant-shared). Saved searches are named, reusable retrieval views (Dataview-style) that bundle a que
- `ctx_saved_searches_create` — Create a new saved search. Supply a unique name (per owner within the tenant), an optional description, the search query string, and the filter blob. Set shared
- `ctx_saved_searches_get` — Fetch a single saved search by id. Returns 404 if it does not exist or the caller cannot see it (different tenant, or owned by another user and not shared).
- `ctx_saved_searches_update`
- `ctx_saved_searches_delete`
- `ctx_saved_searches_run`
- `ctx_run_saved_search`
- `ctx_ingest`
- `ctx_ingest_status`
- `ctx_remember`
- `ctx_events_recent`
- `ctx_memory_review_logs`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@contextq/mcp\"\n      ],\n      \"env\": {\n        \"CONTEXT_API_KEY\": \"<YOUR_CONTEXT_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `CONTEXT_API_KEY` — Context API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; runs locally and hosted.
- Floor 57, ceiling 57 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40contextq%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40contextq%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40contextq%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40contextq%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.