Skip to content
Back to the index

linksee-memory

github.comInfrastructure

PulseGate's liveness check found it on 9 Oct 2026; it has been in the index since 8 Sep 2026. How this is checked

linksee-memory is a local-first MCP server that gives AI agents persistent, cross-agent memory. It uses file-diff caching to reduce repeated context and token usage, and is intended for developers building agent workflows.

Inferred · not functionally tested

WebSelf-hostedCLIAPI
linksee-memory preview
Visit github.com

Overview

6 features

Purpose: Keeping AI agent memory persistent, shareable across agents, and efficient without repeatedly sending unchanged files.

Inferred · not functionally tested

Audience: AI agent developers

Inferred · not functionally tested

Functions: agents

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, self_hosted, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Memory & skills space, linksee-memory takes a focused approach. Inferred · not functionally tested: It focuses on keeping AI agent memory persistent, shareable across agents, and efficient without repeatedly sending unchanged files. Inferred · not functionally tested: linksee-memory is an open-source project aimed at AI agent developers. Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.

Behind linksee-memory is Synapse Arrows. Inferred · not functionally tested: Among its 6 catalogued features are persistent memory, cross-agent sharing, and file diff cache. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Persistent memory
  • Cross-agent sharing
  • File diff cache
  • Token saving
  • Local-first storage
  • MCP server

Topics: Inferred · not functionally tested

Tags
agent-memorymcp-serverlocal-firstfile-diff-cache
AI capabilities
TextStructured
Inference: Local

JSON profile · Text profile · Access guide

Built with & integrations

Connectors
MCP
Runs on
BrowserSelf-hostedCLIAPI-only

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed8 Sep · 09:26 UTC
    io.github.michielinksee/linksee-memory seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about linksee-memory

What does linksee-memory do?
Inferred · not functionally tested: Linksee-memory focuses on keeping AI agent memory persistent, shareable across agents, and efficient without repeatedly sending unchanged files. It is catalogued under Memory & skills on PulseGate.
Who should use linksee-memory?
Inferred · not functionally tested: linksee-memory is an open-source project built for AI agent developers.
What platforms does linksee-memory run on?
Basis unknown · not verified: linksee-memory runs on the web, the command line, and API. It can also be self-hosted.
Is linksee-memory still active?
PulseGate's liveness check found it on 9 Oct 2026.
What are alternatives to linksee-memory?
Similar projects tracked by PulseGate include Memorys, neuromcp, and MCP Light Memory.MemorysneuromcpMCP Light Memory
Who makes linksee-memory?
linksee-memory is developed by Synapse Arrows.
Does linksee-memory have an API or integrations?
Inferred · not functionally tested: Yes — linksee-memory exposes an MCP server.

Similar projects

Closest matches by what these projects do