All MCP Servers
AI & MemoryMCP RegistrypypiB · 73

devin-memory MCP server

io.github.Icaro0310 · Updated

Anti-poisoning memory for agents: provenance, conflicts, quarantine gate.

At a glance

devin-memory is an MCP server in the AI & Memory category. It runs locally over stdio via `uvx devin-memory-mcp`, and declares no required credentials. It scores B (73/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install devin-memory in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install devin-memory in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add devin-memory -- uvx devin-memory-mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What does devin-memory need from you?

Configuration only — Declares config values but no credentials.

  • DEVIN_MEMORY_DBoptionalEnvironment variable

    Path to memory.db (default: ./memory.db)

Pass secrets through your shell environment rather than committing them into a config file.

What tools does devin-memory expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Source analysis currently covers npm packages only. This server ships as a Python package, which needs a different parser.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.

    Client compatibility

    Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

    Health score

    B · 73

    Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

    • Maintenance30%not measurable

      No commit history available.

    • Adoption20%not measurable

      No usage data available.

    • Transparency20%50%

      2/4: ✓ public source repo, ✗ declared license, ✓ documentation, ✗ discoverable tool list.

    • Provenance15%75%

      Links to its own repository; package linkage unverified.

    • Packaging15%100%

      Publishes a pinned version (0.3.1).

    Documentation

    Full README

    Part of the [DEVIN ecosystem](https://github.com/Icaro0310/awesome-devin) Track: Build · Nature: product For: AI engineers, Developers, Data Scientists Interface: CLI / Python library / MCP server / Service Path: AI engineers · step 3/3 — after devin-orchestrator

    Where this fits

    devin-memory

    Renamed (Oct 2026): this repository moved from Icaro0310/devin-memory to Icaro0310/devin-brain — the PyPI package, CLI commands and MCP server name stay devin-memory; stars, issues and history are preserved by the GitHub redirect.

    Unofficial community project. Not affiliated with, endorsed by, or sponsored by Cognition AI. "Devin" is a trademark of Cognition AI.

    [Linux](README.linux.md) · [Personal Windows](README.windows.md) · [Corporate Windows](README.corporate-windows.md)

    Part of the awesome-devin ecosystem: the curated hub for the devin-* tools.

    An anti-poisoning memory store for Devin: durable facts with provenance, versioning, and a quarantine gate — so agent memory can't be silently corrupted by a bad session or injected content.

    The problem

    Agent memory is a poisoning vector. Any tool that persists "facts" between sessions can be corrupted by a single bad session — an injected instruction or a pasted secret becomes a trusted belief in every future session, with no review step and no way to answer *"where did this come from?"*.

    Prior art

    • The Devin memory MCP (retain/recall/reflect over

    .devin/memory/memories.jsonl) — append-only, no screening, no session provenance. devin-memory exports to that exact line shape.

    Excerpt — the full document is on GitHub.

    Maintain devin-memory? Add a badge to your README

    Shows its health grade, and links readers to install steps for every client.

    markdown
    [![devin-memory on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-icaro0310-devin-memory)](https://mcp-skills-hub.vercel.app/mcps/io-github-icaro0310-devin-memory)

    Catalog data refreshed . Something wrong? Report it.