Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Cuemap MCP

by cuemap-devversion 0.7.5i★ –iRuns on your computer
Registry nameio.github.cuemap-dev/cuemap-mcp

Install

Overview

Description from the maker (original English)

Local memory and context retrieval for AI agents through CueMap.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "cuemap": {
      "command": "npx",
      "args": [
        "-y",
        "cuemap-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add cuemap -- npx -y cuemap-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "cuemap": {
      "command": "npx",
      "args": [
        "-y",
        "cuemap-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cuemap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cuemap-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account cuemap-dev, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7251 servers in this category
  • Published to the registry more recently than 64% of the other 7251 servers in this category
  • Basic checks equal to or better than 100% of the other 7251 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Cuemap MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.5) reached the registry 21 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

CueMap MCP Server v0.7.5

A premium MCP bridge for explainable, repository-aware agent memory.

The Model Context Protocol (MCP) server for CueMap, allowing AI coding assistants (like Claude Desktop, Cursor, Windsurf, and Antigravity) to instantly recall codebase context using the CueMap engine.

For agent-facing operating guidance—including repository consent, supported content types, recall modes, accuracy-oriented knob selection, and troubleshooting—see SKILL.md.

Zero-Config Deployment

The CueMap MCP Server is designed to work completely out-of-the-box. When started, it automatically manages a high-performance Rust instance of the CueMap Server in the background. The v0.7.3 engine bundles qint8 MiniLM-L3 by default and q4 MiniLM-L3 for the edge profile; no model download occurs at runtime.

You do not need to install or run the CueMap CLI manually. The correct pre-compiled binary for your operating system is automatically downloaded via optional NPM dependencies. Embedded startup supports Linux x64/ARM64, macOS x64/ARM64, and Windows x64.

Installation

# Global installation makes the `cuemap-mcp` command available

npm install -g cuemap-mcp

*(Note: Ensure your package manager is configured to download optionalDependencies so the local Rust binary is included).*

Agent Plugin

CueMap also ships a separate cuemap-agent-plugin package for Agent Plugins-compatible clients. It bundles the portable plugin.json manifest, stdio mcp.json configuration, and a repository-memory skill. The plugin launches this MCP server at the matching release version and must be installed or downloaded separately from cuemap-mcp.

Configuration (Environment Variables)

By default, the embedded engine runs on port 8735. You can customize the server behavior by passing the following environment variables in your MCP configuration:

  • CUEMAP_PORT: Override the port the embedded engine binds to (default: 8735).
  • CUEMAP_CONFIG_PATH: Absolute path to a custom server_config.toml to configure advanced Engine tuning, background jobs, and RAG search parameters.
  • CUEMAP_URL: If you prefer to bypass the embedded engine and connect to a remotely hosted or separately running CueMap server, specify its URL here (e.g. http://localhost:8735).
  • CUEMAP_PROJECT: Override the default project. Without this setting, CueMap derives a stable repository-scoped project from the current Git remote or working directory.
  • CUEMAP_LOG_PATH: Override the embedded engine log path. It defaults to ~/.cuemap/server.log, which is the file read by cuemap logs.
Server lifecycle

The MCP server calls EmbeddedCueMap.start() as soon as Codex launches the plugin process, before any CueMap tool is invoked. It attaches to a compatible engine already listening at CUEMAP_URL or the configured port; otherwise it starts and owns a local engine automatically. cuemap_init does not start the server—it previews or applies a confirmed repository scope after the engine is ready. An engine owned by the MCP process is stopped gracefully when that process exits.

Using with AI Agents

To use this MCP server with your AI assistant, add it to your assistant's MCP configuration file.

Example Configuration (Claude Desktop)
{

"mcpServers": { "cuemap": { "command": "npx", "args": [ "-y", "cuemap-mcp" ], "env": { "CUEMAP_PORT": "8735" } } } }

Available Tools

  • `cuemap_init_preview`: Performs a read-only repository metadata scan and returns supported top-level folders/root files, counts, the stable repository project ID, and any existing saved scope. Present this preview to the user before ingestion.
  • path (string): Absolute path to the repository root.
  • projectName (string, optional): Project ID override. Defaults to the stable repository-scoped ID.
  • includedPaths (string[], optional): Repository-relative files or folders to preview. Empty means all supported files allowed by ignore rules.
  • ignoredPatterns (string[], optional): Additional gitignore-style exclusions.
  • ignoredExtensions (string[], optional): Additional excluded extensions.
  • `cuemap_init`: Applies a user-confirmed repository ingestion scope, starts the initial scan, and keeps watching that scope for new, changed, deleted, newly ignored, or newly unignored supported files. It only reports verified completion after observing ingestion activity, reaching a terminal job phase, and completing intent annotation; an initial idle status with 0/0 writes is not considered complete.
  • path (string): Absolute path to the repository root.
  • projectName (string, optional): Project ID override. Defaults to the stable repository-scoped ID.
  • includedPaths (string[], optional): User-approved repository-relative files or folders. Empty means all supported files allowed by ignore rules.
  • ignoredPatterns (string[], optional): Additional gitignore-style exclusions.
  • ignoredExtensions (string[], optional): Additional excluded extensions.
  • confirmed (boolean): Must be true only after explicit user confirmation of the previewed scope.
  • `cuemap_status`: Returns project-scoped background ingestion progress plus derived monitoring fields. Poll it after cuemap_init until verified_complete is true.
  • project (string, optional): Project ID override. Defaults to the stable repository-scoped ID.
  • active: Whether the current phase is non-terminal or writes/intent annotations remain pending.
  • observed_activity: Whether this MCP process has observed an active phase or positive write/intent counts for the project.
  • pending_writes: Remaining writes based on the latest totals.
  • pending_intents: Remaining memory intent annotations based on the latest totals.
  • verified_complete: True only after activity has been observed, the project reaches done or idle, no work failed or remains pending, and intent_ready is not false.
Project inspection and memory lifecycle
  • `cuemap_projects`: List projects and their summary metadata, including whether each project is currently loaded in RAM.
  • `cuemap_project_load`: Explicitly warm a persisted project before a latency-sensitive operation. Ordinary project requests demand-load it when needed.
  • `cuemap_project_save`: Persist a current snapshot without unloading it.
  • `cuemap_project_unload`: Persist and unload a project to reduce memory usage. Active work can produce a retryable busy response.
  • `cuemap_project_pack` / `cuemap_project_package_load`: Write or load a ready-to-query local .cuemap package.
  • `cuemap_project_push` / `cuemap_project_pull`: Transfer a package through S3 using the engine host's configured AWS CLI.
  • `cuemap_project_sync`: Fast-forward immutable S3 history and refuse divergence.
  • `cuemap_stats`: Read repository-project statistics, or global engine statistics with global: true.
  • `cuemap_memory_get`: Read one memory as decoded text and provenance by numeric memory_id and owning project. Requires an engine supporting GET /memories/:id?decoded=true; older engines return an upgrade error through this tool.
  • `cuemap_memory_reinforce`: Reinforce one memory, optionally on explicit cues.
  • `cuemap_memory_delete`: Permanently delete one memory. Requires confirmed: true after explicit user confirmation.
  • `cuemap_project_export`: Export a cursor-paginated project page with configurable content, cue, and metadata inclusion.
  • `cuemap_project_artifacts`: Inspect CueBridge artifact metadata without reloading it.
Explicit ingestion
  • `cuemap_ingest_url`: Ingest one URL or recursively crawl it with depth and same_domain_only controls.
  • `cuemap_ingest_content`: Ingest supplied text with filename, source-key, metadata, structural-cue, segmentation, and optional one-vector-per-produced-chunk embeddings.
  • `cuemap_ingest_file`: Ingest one user-approved local file path.

These tools are for explicit ingestion requests. Repository initialization continues to use the preview, confirmation, and watcher workflow above.

Alias and Lexicon administration
  • `cuemap_alias_list`, `cuemap_alias_add`, `cuemap_alias_merge`: Inspect and manage manual cue aliases. Merging requires confirmed: true.
  • `cuemap_lexicon_inspect`, `cuemap_lexicon_graph`, `cuemap_lexicon_wire`, `cuemap_lexicon_delete`: Inspect and administer Lexicon relationships. Deletion requires confirmed: true.
  • `cuemap_add`: Stores one natural-language memory. The project is created automatically if it does not exist.
  • content (string): Memory content to store.
  • project (string, optional): Project ID that will own the memory. Defaults to the current repository-scoped project.
  • cues (string[], optional): Explicit cues/tags to associate with the memory.
  • metadata (object, optional): JSON metadata to store with the memory.
  • source_key (string, optional): Stable source key for deterministic upsert/deduplication.
  • event_time (number, optional): Original event timestamp as Unix seconds. Defaults to ingestion time.
  • embedding (number[], optional): Precomputed memory embedding.
  • disable_temporal_chunking (boolean, optional): Disable temporal chunking for this memory.
  • async_ingest (boolean, optional): Process ingestion in the background and return immediately.
  • `cuemap_intent_classify`: Classifies text with the engine's local intent model. Accepts target: "query" or "memory" and returns relative intent scores, recall/memory eligibility, confidence weight, and model/taxonomy versions. Scores are ranking signals, not calibrated probabilities.
  • `cuemap_recall`: Recalls context about a codebase from your CueMap integrated brain. Uses natural language and semantic search to find relevant information.
  • query (string): The natural language query to search for.
  • limit (number, optional): Maximum results to return (default: 10).
  • response_mode (full | preview, optional): Default full. Use preview for broad discovery; each hit returns a leading excerpt instead of full content, retaining IDs and metadata.
  • preview_chars (integer, optional): Preview length cap, 100–2000 UTF-16 code units (default: 200). Ignored in full mode. Metadata and diagnostics are not capped.
  • projects (string[], optional): List of project IDs to scope the search to. Multiple enables cross-project queries.
  • cues (string[], optional): Specific cue tags to filter the search.
  • query_time (string, optional): Timestamp or natural-language time anchor for v0.7 temporal query intent.
  • depth (number, optional): Depth of multi-hop recall expander (default: 1).
  • expansion_depth (number or "conversation_round", optional): Neighbor context expansion (default: "conversation_round"). Values above 1 include nearby parent chunks or source-ordered context, using a radius of expansion_depth - 1 when linkage exists. "conversation_round" prepends the message each result replies to (for an assistant reply, t

Only the beginning is shown; read the rest in the repo

Ask PopNx