threadline-mcp
Related Servers
Alternatives to threadline-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.MIT
- AlicenseAqualityBmaintenanceMCP server for Statewave, an open-source memory runtime for AI agents. Provides persistent memory, context retrieval, and memory compilation through the Model Context Protocol.613 npm4Apache 2.0

Structured-shofficial
AlicenseNot gradedqualityNot gradedmaintenanceMCP server providing managed persistent memory for AI agents. Read and write structured state across sessions, tools, and restarts at 1000+ requests per second, with no infrastructure to self-host or operate.2Apache 2.0- AlicenseNot gradedqualityBmaintenanceMCP server providing persistent AI memory with four-tier retrieval (SQLite FTS5, graph, vector, LLM agent) to give AI assistants structured, long-term memory without RAG.1Apache 2.0
- AlicenseAqualityBmaintenanceA self-hosted MCP memory server that gives every MCP-compatible agent a shared, persistent memory layer, so preferences, project conventions, and past decisions carry across sessions and across different agents and vendors. It combines hybrid keyword-plus-vector retrieval with automatic context injection, zero-config sync, and selective injection of memories by agent and priority.202MIT
- AlicenseNot gradedqualityDmaintenanceSelf-hosted personal context layer that gives AI agents shared memory via MCP.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'inject' handles pre-LLM call context insertion, while 'update' handles post-interaction context extraction and storage. There is no overlap in functionality, making them easily distinguishable for an agent.
Both tools use simple, imperative verb names ('inject' and 'update') that are consistent in style and length. This follows a predictable pattern without any deviations or mixed conventions.
With only 2 tools, the server feels thin for its apparent purpose of managing user context across LLM interactions. A typical context management system might benefit from additional operations like retrieving or deleting context, making this set under-scoped.
The tools cover the core workflow of injecting and updating user context, but there are notable gaps. For example, there is no tool to retrieve stored context for review or delete outdated context, which could limit agent functionality in multi-session scenarios.