原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Pmll Memory MCP

作者:drQedwards版本 0.1.1i★ –i在你的电脑上运行
注册名称io.github.drQedwards/pmll-memory-mcp

安装

概览

作者提供的说明(英文原文)

PMLL Memory MCP — persistent KV context memory and Q-promise deduplication.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

claude mcp add pmll-memory -- npx -y pmll-memory-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 drQedwards 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

  • 星标数多于此分类中其他 7277 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 7277 个服务器的 4% 更新
  • 基础检查结果等于或优于此分类中其他 7277 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Pmll Memory MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.1)于8个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者:upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT昨天更新
安装

Codebase Memory

作者:DeusData

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

在你的电脑上运行★ 48,148MIT21天前更新
安装

Exa

作者:exa-labs

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

在云端运行★ 5,213MIT上个月更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

PPM — Python Package Manager

pypm packaging CLI with shared PMLL memory + Q-promise. Sibling: drQedwards/pmll.

Live Stellar pmll-anchor IDs: docs/STELLAR.md · skills: SKILL.md · promises: Q_promise_lib/README.md.

TL;DR: PPM packages Python (C CLI). Shared PMLL owns memory/state (memory_silo_t, exact peek + semantic peek_semantic,

SAT bridge, init_pml). Q-promise owns temporal/control-flow (qpromise_*, libqpromise.so)

— it does not replace the silo. Optional Stellar commitments hash off-chain

CodeworkPayloads into 32-byte digests via pmll-anchor (ABI: init/store/get/bump).

Companion packaging CLI + MCP memory server live in-tree.

PMLL provides durable structured memory for agent workflows, alongside a PPM packaging CLI (hermetic bundles, plugins, signing) and the PMLL Memory MCP server. Long-term graph tools adapt Context+.


Table of Contents

  1. Layers (post-merge)
  2. Features
  3. Building from Source
  4. CLI Commands
  5. GPU & Security Features
  6. Plugin System
  7. Configuration
  8. PMLL Memory MCP Server
  9. Stellar commitments
  10. Architecture
  11. Release Notes
  12. Roadmap
  13. Contributing & Sponsors


Layers (post-merge)

Two complementary layers — not substitutes for each other:

LayerOwnsKey surface
PMLLDurable memory / statememory_silo_t, peek / peek_semantic, silo_set, SAT bridge, init_pml
Q-promiseTemporal / control-flowqpromise_* API, libqpromise.so, deferred qpromise_drain()

Q-promise does not replace the silo. A promise may *reference* a memory key (and optional SAT state id); results are committed back with silo_set / qpromise_resolve_commit.

Intended loop
retrieve (peek / peek_semantic)

→ compute / request work → promise PENDING → resolve / reject (optionally resolve_commit → silo) → continuation (then / catch / finally via qpromise_drain) → memory update → retrieve again

Thread safety: the C Q-promise drain is single-threaded. Continuations run only during qpromise_drain() on the calling thread; callers must externally serialize access. Details: Q_promise_lib/README.md.

C core (PMLL)

Headers: PMLL.h · implementation: PMLL.c

SymbolRole
memory_silo_tAssociative/semantic silo: tree, slots[], embed_dim (PMLL_EMBED_DIM=32), slot_count
silo_slot_tkey, content, embedding, resolved
init_silo / free_silo / silo_setAllocate, free, write key/content + embedding
peekExact key, else index
peek_semanticCosine ≥ min_sim over embeddings (silo_embed_text, silo_cosine_similarity)
init_pmlSets every assignment[i] = -1 (undecided)
check_conflictTreats -1 as undecided (not sticky false from zero-fill)
sat_bridge_*Map 3SAT tokens → associative string literals in the silo
Q-promise library

Build / test / API: [`Q_promise_lib/README.md`](Q_promise_lib/README.md) (authoritative). Public symbols are qpromise_*; shared object is libqpromise.so. The old prototype (QMemNode / q_mem_* / memory-chain walker) is removed; Q_promises.h is a compatibility include redirecting to qpromise.h.

✨ Features

CommandWhat it does
pypm doctorChecks Python headers, C compiler, OpenSSL, WASI toolchain, GPU, …
pypm sandbox [-d DIR]Drops you into an ephemeral temp dir (or custom DIR) with a full shell
pypm plugin add NAME SRCDownloads a .so plugin (from URL or path) into ~/.pypm/plugins/
pypm plugin run NAME …Executes pypm_plugin_main() inside the named plugin
pypm pypylock [-o FILE]Bundles every wheel + interpreter into dist/venv.tar.gz (or FILE)
pypm versionPrints the current CLI version
ppm import PKGImport and cache a package with GPU-accelerated hash verification
ppm add PKG --lockAdd packages and update the lockfile
ppm plan / ppm applyPlan dependency changes, then apply them with an audit trail
ppm snapshot / ppm rollbackSnapshot the environment; roll back to any prior state
ppm sign / ppm verifySign artifacts (Ed25519) and verify cryptographic receipts
ppm sbomGenerate a Software Bill of Materials (SBOM)

*Road-mapped:* SAT dependency solver (the standalone SAT.c CDCL solver exists but is not yet used for resolution), parallel wheel cache, workspaces with single lockfile, WASM wheel resolution, Conda & Poetry import plugins.


🔧 Building from Source

System dependencies
  • C11 compiler (gcc, clang, or MSVC)
  • libcurl (plugin downloads)
  • libdl (dynamic loading — standard on Linux / macOS)
  • tar / libarchive (optional, for pypylock bundles)
Build & first run
git clone https://github.com/drQedwards/PPM.git

cd PPM cc -Wall -Wextra -ldl -lcurl -o pypm Ppm.c ./pypm doctor # Diagnose your dev box ./pypm sandbox # Spin up a throw-away REPL playground

Q-promise shared library
cd Q_promise_lib

make clean && make test make shared # → libqpromise.so cd ..

Optional: CUDA-accelerated build
nvcc -O3 CLI/CLI.cu -lcuda -o ppm-gpu

./ppm-gpu import transformers torch --verbose


🖥 CLI Commands

Import packages
# Import a single package

ppm import transformers

Import with a specific version

ppm import transformers==4.43.3

Import multiple packages

ppm import transformers torch numpy

Scan a Python file for imports and install them

ppm import --from-file my_script.py

Verbose — watch what's happening

ppm import transformers --verbose

🔍 Resolving transformers...

⬇️ Downloading transformers-4.43.3-py3-none-any.whl

🔐 GPU integrity check: PASSED

✅ transformers==4.43.3 imported successfully

Project initialization
ppm init

Creates:

.ppm/

├── ledger.jsonl ← append-only operation log

├── state.json ← current state

├── lock.json ← dependency lockfile

└── snapshots/ ← rollback points

Dependency resolution & locking
ppm add transformers torch==2.4.0 --lock

ppm plan

{ "plan": "install", "packages": { "transformers": "4.43.3", ... } }

ppm apply --note "Added ML stack"

Snapshot & rollback
ppm snapshot --name "before-upgrade"

ppm snapshots ppm rollback before-upgrade

Environment diagnostics
ppm doctor

✅ Python dev headers found

✅ C compiler available

✅ CUDA toolkit available

🏁 Diagnostics complete (0 issues found)

Sandbox
ppm sandbox                 # ephemeral temp directory

ppm sandbox -d /tmp/mydir # custom directory

Hermetic packaging
ppm pypylock -o production-env.tar.gz

🔐 GPU & Security Features

GPU-accelerated hash verification
ppm import torch --verbose

🚀 GPU hash verification: SHA-256 computed on device

✅ Integrity verified: e3b0c44298fc1c149afbf4c8996fb924...

GPU backend selection
ppm ensure transformers --gpu auto    # auto-detect CUDA

ppm ensure transformers --gpu cu121 # force CUDA 12.1 ppm ensure transformers --gpu cpu # CPU-only

Ed25519 cryptographic signing
ppm keygen --out-priv ed25519.priv --out-pub ed25519.pub

ppm sign --sk ed25519.priv --file torch-2.4.0-*.whl --gpu ./libbreath_gpu.so ppm verify --receipt torch-2.4.0-*.whl.receipt.json --file torch-2.4.0-*.whl

Provenance & SBOM
ppm sbom        --out project-sbom.json

ppm provenance --out provenance.json ppm graph --dot | dot -Tpng -o deps.png


🔌 Plugin System

# Install a plugin

ppm plugin add auditwheel https://cdn.example.com/auditwheel.so

Run it

ppm plugin run auditwheel repair --wheel torch-2.4.0-cp310-linux_x86_64.whl

Writing a plugin (C)
// hello.c

#include int pypm_plugin_main(int argc, char **argv) { puts("Hello from a plugin 👋"); return 0; }

cc -shared -fPIC -o hello.so hello.c

mv hello.so ~/.pypm/plugins/ pypm plugin run hello


⚙️ Configuration

pypm.toml
[tool.ppm]

python = "^3.10" default_gpu = "auto"

[tool.ppm.backends] cpu.index = "https://download.pytorch.org/whl/cpu" cu121.index = "https://download.pytorch.org/whl/cu121" cu122.index = "https://download.pytorch.org/whl/cu122"

torch_prefer = "2.4.*" transformers_prefer = "4.43.*"

Environment variables
export PYP_WORKSPACE_ROOT=/path/to/project   # override workspace detection

export PYP_DEBUG=1 # enable debug output export CUDA_VISIBLE_DEVICES=0 # control GPU usage


🧠 PMLL Memory MCP Server

**Persistent memory logic loop with short-term KV context memory, Q-promise

deduplication, and Context+ long-term

memory graph designed to improve context retention and retrieval for coding agents.**

pmll-memory-mcp is a Model Context Protocol (MCP) server with complementary short-term KV and optional long-term graph layers. Server construction prefers MCPServer (mcp 2.x) and falls back to FastMCP (mcp 1.x) — see mcp/pmll_memory_mcp/server.py.

Ground tool names in code: TypeScript (mcp/src/index.ts) has 15 tools including graphql and names like create_relation; Python (mcp/pmll_memory_mcp/server.py) has 14 tools (no graphql) with several longer names such as create_memory_relation. A ctypes demo in Ppm-lib/pmll_mcp/ loads libqpromise.so via qpromise_*.

Memory layers:

  • Short-term KV cache (5 tools) — session-isolated key-value memory with Q-promise deduplication, mirroring PMLL.c::memory_silo_t.
  • Long-term memory graph (6 tools) — adapted from Context+ by @ForLoopCodes, providing a SQLite-backed property graph with typed nodes, weighted edges, temporal decay scoring (e^(-λt)), and semantic search via stable hashing embeddings.
  • Solution engine (3 tools) — bridges both layers with unified context

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx