Neuron - "Synapse"
Related Servers
Alternatives to Neuron - "Synapse"
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides AI assistants with persistent, semantic memory using Turso for storage and OpenAI for vector search. It enables natural language operations to store, retrieve, and refine information with automatic duplicate detection and quality validation.53 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides persistent semantic memory backed by PostgreSQL and pgvector for storing and searching thoughts via vector embeddings. It enables dimensional organization, conflict detection, and historical tracking of facts, decisions, and observations.5 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceOpen-source MCP server that gives any LLM long-term memory using a knowledge graph and vector search hybrid. It stores entities, observations, and relationships, enabling semantic recall across sessions with automatic clustering and fail-loud infrastructure.51MIT
- AlicenseNot gradedqualityCmaintenancePersistent semantic memory server for AI assistants via MCP, enabling long-term context retention and semantic search across conversations.11MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server that provides long-term memory for LLMs by storing and retrieving important facts, decisions, and preferences through smart semantic search and automatic organization.12MIT
- AlicenseNot gradedqualityAmaintenanceA universal MCP server providing persistent, structured memory through a knowledge graph with graph storage, semantic vector search, and multi-hop traversal for AI agents and IDEs.1MIT
TDQS
Scored across 22 tools
There are overlapping purposes among retrieval (get_context, pre_turn, vector_search, find_candidates) and maintenance commands (consolidate, merge, prune), but detailed usage notes help an agent choose. Still, find_candidates vs vector_search and consolidate vs merge are easy to confuse.
The dominant pattern is lowercase snake_case with verb_noun commands like get_context and store_turn, but names like auto, skill, status, forgotten, dedup, and flash break the convention. The style is readable, but not consistently predictable.
22 tools is on the heavy side for a focused memory server, with several that could be merged or hidden behind the core loop (e.g., vector_search/find_candidates, consolidate/merge, status/summary). It is not overwhelmingly large, but it feels padded.
The core lifecycle is covered well: pre-turn retrieval, post-turn storage, context switching, export, and cleanup. Notable gaps include no explicit restore-from-_graveyard tool and no way to delete or edit a single node/link directly.