Remote Memory MCP Server
Related Servers
Alternatives to Remote Memory MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGives every AI agent working in a repository a shared, persistent knowledge graph stored in a plain JSONL file, with each entity, relation, and observation tagged with the date and agent that added it. Provides tools and prompts for searching, editing, renaming, merging, cleaning up, and exporting that memory, and keeps it locked to the repository that owns it.1454 PyPIMIT

Oceanir Memoryofficial
FlicenseNot gradedqualityDmaintenanceProvides persistent long-term memory for AI coding agents by storing entities, relations, and observations across different sessions. It enables users to manage and query structured knowledge like coding preferences, project patterns, and technical solutions via a graph-based storage system.1-- AlicenseBqualityDmaintenanceTransforms a GitHub repository into a structured personal brain for AI to manage tasks, notes, and goals through markdown files. It enables direct interaction with a version-controlled knowledge base, allowing for automated organization and efficient retrieval of information.1510 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to store, query, and update persistent project knowledge as a local, Git-friendly knowledge graph, providing structured memory across sessions.9Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides persistent memory for Claude by implementing a local knowledge graph to store and retrieve entities, relations, and observations. This enables long-term information retention and personalization across different chat sessions.207,413 npm-
- AlicenseNot gradedqualityBmaintenanceEnables agents to read, search, and propose durable knowledge stored as flat files in a GitHub repository, with every write opened as a pull request and domain owners approving changes in a web UI without touching git.Apache 2.0
TDQS
Scored across 17 tools
Most tools have distinct purposes, but there is some overlap between list_entities, get_entity_names, open_nodes, and search_nodes, which all involve retrieving entity information and could cause confusion. However, their descriptions provide enough detail to differentiate them in most cases.
The tool names follow a highly consistent verb_noun pattern throughout, such as add_observations, create_backup, and delete_entities. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 17 tools, the count is slightly high but reasonable for a memory/graph management server, covering operations like CRUD, synchronization, and queries. It might feel a bit heavy, but each tool appears to serve a specific function without obvious redundancy.
The tool set provides comprehensive coverage for managing a knowledge graph with entities, relations, and observations, including full CRUD operations, synchronization with GitHub, backup, and various query methods. There are no apparent gaps that would hinder agent workflows in this domain.