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

Marm MCP Server

by Lyellr88version 2.60.1i★ –iRuns on your computer
Registry nameio.github.Lyellr88/marm-mcp-server

Install

Overview

Description from the maker (original English)

Universal MCP Server with advanced AI memory capabilities and semantic search.

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

  • PyPIPython’s uv installed (for the uvx 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": {
    "marm": {
      "command": "uvx",
      "args": [
        "marm-mcp-server",
        "stdio"
      ]
    }
  }
}

Run this in your terminal

claude mcp add marm -- uvx marm-mcp-server stdio

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "marm": {
      "command": "uvx",
      "args": [
        "marm-mcp-server",
        "stdio"
      ]
    }
  }
}

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": {
    "marm": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "marm-mcp-server",
        "stdio"
      ]
    }
  }
}

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 Lyellr88, 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 5653 servers in this category
  • Published to the registry more recently than 60% of the other 5653 servers in this category
  • Basic checks equal to or better than 100% of the other 5653 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 Marm MCP Server 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 (2.60.1) reached the registry 26 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker 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 yesterday
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 21 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 2 months ago
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.

marm-memory v2.60.1 - Give your AI Agents a permanent memory in 60 seconds

Contributions welcome! Browse open issues to contribute, or join the MARM Discord to share workflows, get setup help, and connect with other builders.

IMPORTANT

Project Status: Brief Personal Pause

I took a short personal break from active development to focus on matters outside the project. This project is still active, and I plan to return soon to keep building and refining it.

Thank you for your patience, support, and continued interest. I’ll resume work soon and share updates as progress continues.

Table of Contents

  • Quick Start
  • Why MARM Memory
  • MARM Console
  • Performance & Scaling Benchmarks
  • MCP Client Setup
  • Runtime CLI Commands
  • Complete MCP Tool Suite
  • Using MARM: Talk, Don't Call Tools
  • Understanding MARM Memory
  • Knowledge Graphs: Code & Concepts
  • Architecture & Internals
  • Troubleshooting
  • Contributing
  • Project Documentation

Quick Start

  1. Install and initialize with your preferred agent profiles:
pip install marm-mcp-server

marm-memory init --g-claude --g-codex --g-antigravity

Also available: --g-cursor, --g-grok, --g-hermes, --g-opencode, --g-devin, --g-cline, --g-qwen, --g-kiro and --g-zed. Run without flags to install into your current project folder instead of home

  1. Hand off to your AI companion. Tell your agent:

"Use the marm-init skill to set up MARM."

  1. Interact: Your agent will handle the entire setup (Python/Docker, HTTP/STDIO, keys, and client configs) interactively right inside your chat.

Manual setup

Prefer to wire it up yourself:

Replace "agent" with your client’s CLI command (for example, claude, agy, or qwen). For Codex, use codex mcp add marm-memory --url http://localhost:8001/mcp instead.

If you are...Start the serverConnect your MCP client
Solo developer / researchermarm-memory start"agent" mcp add --transport http marm-memory http://localhost:8001/mcp
Private local STDIO usermarm-mcp-stdio"agent" mcp add --transport stdio marm-memory-stdio marm-mcp-stdio
Multiple agents sharing memorymarm-memory start --profile swarm"agent" mcp add --transport http marm-memory http://localhost:8001/mcp
Private high-throughput swarmmarm-memory start --profile swarm-max"agent" mcp add --transport http marm-memory http://localhost:8001/mcp
Trusted private lab/servermarm-memory start --profile trusted"agent" mcp add --transport http marm-memory http://localhost:8001/mcp
  • ⚡ Fastest HTTP Startup: Run marm-memory fast-start-http to spin up the local runtime, launch the console, and open it in your browser immediately.
  • 🖥️ Web Console: Run marm-memory console to view the local UI app instantly (no Node.js required).
  • ⚙️ Lifecycle Management: Manage the background daemon using status, logs --follow, restart, and stop.
  • 💡 Quick Flags: Use --no-console or --no-browser to restrict startups. Run marm-memory --help for full command lists.

Why MARM Memory

Your AI forgets everything. MARM Memory doesn't.

marm-memory gives your agents a private, shared memory for the context that normally gets lost between chats: decisions, research, fixes, notes, and project history. Switch from Claude Code to Codex or Gemini without losing the context already gathered.

It brings three things together:

  • 🧠 Core Memory (8 tools) stores conversations, notes, notebook entries, and summaries so they stay searchable.
  • 💻 Code Graph (6 tools) maps your repository so agents can find symbols, follow code paths, and understand the project without rereading it all. Point it at a repo once and it keeps itself current as you work.
  • 🧩 Concept Graph (2 tools) connects people, decisions, errors, and ideas from your stored memories, with links back to relevant code when available. It builds itself as you store memories.

All 16 tools work over HTTP and STDIO. Your agents share the same local memory across sessions instead of starting from scratch each time. The bundled Console App provides a local control plane for memory, graphs, code context, distillation, runtime controls, and the integrated terminal. Indexing a repository creates its independent Code Graph, which you can explore from Knowledge Graph → Code Explorer even before storing any memories.

How It Works
LayerWhat it doesWhy it matters
Memory modelSessions, structured logs, notebooks, summaries, and semantic memoriesKeeps project history searchable instead of trapped in one chat
Scale layerSQLite WAL mode, connection pooling, serialized write queue, and HTTP rate-limit presetsLets one server support solo use, multi-agent work, and swarm-style bursts
Intelligence layerFTS filter, semantic re-rank, bounded semantic fallback, auto-classification, write-time consolidation, and compaction candidatesKeeps recall useful as memory grows instead of letting duplicates pile up
Code graph layerRepo indexing, symbol lookup, call tracing, architecture overview, and change-impact analysisGives agents project structure without rereading the whole codebase
Concept graph layerEntity and relationship extraction from stored memories, with links back into the code graphConnects decisions, errors, tools, and people across sessions instead of leaving them as flat text
Token layerLightweight 8-tool core surface (16 total with bundled graph tools), semantic re-rank before retrieval, and write-time deduplicationReduces tokens sent to the model on every recall and cost stays predictable as memory scales
Deployment layerPip, Docker, STDIO, HTTP, and managed swarm, swarm-max, and trusted profilesLets you run private local memory or shared multi-agent memory with the same MCP surface

See Performance & Scaling Benchmarks for retrieval latency, concurrency, and write-cost numbers, and Architecture & Internals for the mechanisms behind each layer.

MARM Console: Your Local Control Plane

Run marm-memory console to open the bundled web app at http://127.0.0.1:8002. It ships with MARM, needs no Node.js installation, stays on your machine, and works with the same local stores and MCP runtime your agents use.

WorkspaceWhat it gives you
Memories and Knowledge GraphBrowse, filter, edit, and clean up memory, logs, notebooks, extracted concepts, duplicates, concept builds, and code links.
Indexed Projects and Project ExplorerIndex local repositories, inspect architecture, impact, coverage, decisions, runtime traces, symbol search, and code-graph topology.
Code ContextBuild one bounded view of task-ranked symbols, source, and related memory. An optional local model can answer from that same context, with its citations checked.
DistillTurn transcripts into durable-memory proposals. Review, apply, or discard them with duplicate evidence visible.
System and TerminalManage runtime health, indexing, local-model settings, backups, diagnostics, and maintenance. The docked terminal provides a real local shell with persistent sessions and a searchable MARM command menu.
ConnectionsSet up MARM end to end in one place. Setup connects Claude Code, Claude Desktop, Cursor, VS Code, Codex CLI, Grok Build, Hermes Agent, OpenCode, Cline, Antigravity, Qwen Code, Devin, Kiro, and Zed over HTTP, STDIO, or Docker STDIO, tests each connection, and saves server settings to ~/.marm/settings.json. Docker pulls, starts, and stops the MARM container and writes a compose file. Manual gives copy-ready config for each client and OS, every CLI command, and every HTTP endpoint.
Runtime CLI Commands

marm-memory is the local runtime manager installed with the Python package. These are the normal operational commands; use marm-memory --help for flags and command-specific examples.

Daily runtime work

marm-memory fast-start-http                # start HTTP, Console, and open the browser

marm-memory fast-start-http --client cursor # also connect one client (add --transport stdio for STDIO) marm-memory start # start or reuse the managed HTTP runtime marm-memory start --profile swarm # shared multi-agent preset marm-memory stop # stop the managed runtime safely marm-memory restart # restart the managed runtime marm-memory status # inspect runtime, database, queue, and graph status marm-memory logs --follow # follow bounded runtime logs marm-memory console # start or reuse the bundled local Console

Transports and setup

marm-memory http                           # run HTTP in the foreground

marm-memory stdio # run the strict local MCP STDIO transport marm-memory init # install the MARM skill into detected agents (project scan) marm-memory init --g-claude # install the skill into the home-folder claude directory marm-memory doctor # diagnose the local install marm-memory key init # create or reuse ~/.marm/.env without displaying the key marm-memory key path

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

Ask PopNx