MCP Memory Graph

io.github.RetroRobAIPublished by GitHub account RetroRobAIv0.1.1Updated Oct 24, 2026

Authority-weighted memory graph for AI agents with conflict detection and semantic search.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

A local memory graph server that gives an AI assistant persistent, authority-weighted memory with conflict detection and semantic search.

What you can do
Provides an authority-weighted memory graph for AI agents, letting an assistant store and retrieve remembered information. It includes conflict detection to flag contradictory entries and semantic search to find relevant memories by meaning rather than exact keywords. It runs as a local process over stdio.
When to use it
Worth adding when an assistant needs to carry context across sessions or tasks and you want conflicting facts surfaced rather than silently overwritten. Useful for long-running agent workflows where recall quality matters.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package mcp-memory-graph over stdio. Desktop only; no web execution. No authentication, environment variables, or headers are declared.
Before you install
The manifest declares no credentials, keys, or accounts, and no write, send, or delete behavior is described. Memory content is stored locally, so treat anything remembered as retained on the machine. Details of storage location and retention are not documented in the available input.

Installation

In SourceWeft

  1. Open MCP Memory Graph in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations