Telys
OfficialRelated Servers
Alternatives to Telys
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to store, retrieve, and manage persistent memories locally via an MCP server with hybrid vector and keyword search, plus tools for memory CRUD, search, backup, and import.MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.1 npmMIT

synapse-layerofficial
AlicenseBqualityAmaintenanceMCP-native persistent memory for AI agents. Stores and retrieves encrypted memories with Trust Quotient scoring, cross-agent handover protocol, and immutable audit trail. 13 tools. Remote endpoint available.1313Apache 2.0
Enigma MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceOffers MCP tools for managing a local AI memory vault, including remembering, searching, context packing, deletion, and verification of receipts.34 npm1Apache 2.0- AlicenseNot gradedqualityBmaintenanceProvides persistent memory for AI coding agents, enabling them to save, search (hybrid vector/BM25/concept graph), list sessions, and forget memories via MCP tools.11 npmApache 2.0
- AlicenseAqualityAmaintenanceUnified MCP server: hybrid search + code graph + semantic memory. 10 tools, <350MB RAM, fully local. No API keys.1033 PyPIPolyForm Noncommercial 1.0.0
TDQS
Scored across 19 tools
Every tool targets a distinct resource and action: separate search paths (semantic, lexical, repo), distinct write operations (add, upsert, update, delete), and clear maintenance tools (build indexes, compact, tune). Overlapping functions like telys_ids vs telys_count are explicitly differentiated in descriptions. No two tools appear to do the same thing.
All tools follow the consistent `telys_` prefix with snake_case and a verb_noun pattern (e.g., build_lexical, search_lexical, list_collections, index_repo). A few like telys_ids and telys_stats are noun-only but still clearly named and stylistically uniform, so no mixing of conventions.
At 19 tools, the set is slightly heavy but each tool earns its place for a full-featured memory/vector search server with repo indexing. The count is on the higher end of reasonable, but the scope justifies it; it does not feel bloated.
The tool surface covers the full lifecycle: collection creation, listing, stats, CRUD operations (add, upsert, update, delete, get), multiple search paths, index building and maintenance, and repo-specific indexing/search. The only notable gap is a missing delete_collection tool, which agents cannot work around easily.