HomarUScc
Related Servers
Alternatives to HomarUScc
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to retain persistent identity, cross-session memory with semantic search, and behavioral pattern tracking across sessions. It lets the agent save and recall facts, decisions, and lessons locally, record interaction signals, run reflection cycles, and evolve frameworks based on accumulated evidence.6 npmMIT
- AlicenseNot gradedqualityCmaintenanceTransforms Claude into a persistent intelligence layer with automatic checkpointing, crash recovery, semantic memory, and cross-project learning. It provides 128+ tools for session management, adversarial testing, and browser automation to eliminate state loss and context rebuild costs.52 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables running Claude Code 24/7 from Telegram, including voice-note transcription and voice replies, persistent conversation memory across restarts, scheduled reminders and calendar access, and live monitoring of tool calls and agent sessions.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code with persistent memory that learns from past sessions, capturing coding episodes and surfacing relevant memories to improve over time.6Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables running and controlling Claude Code 24/7 through Telegram with two-way voice messages, persistent memory across restarts, scheduled reminders, Google Calendar access, and live visibility into every tool call via Agentic Mode.-
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to persist identity, memory, and behavioral patterns across sessions through an MCP server with 15 tools, providing semantic memory search, automatic correction tracking, and evolving frameworks. It lets users recall past decisions, monitor recurring mistakes with trend analysis, and let judgment develop over time — all locally with no cloud dependency.6 npmMIT
TDQS
Scored across 59 tools
Multiple tools have overlapping purposes, such as memory_search, memory_search_multi, vault_search, docs_search, and obsidian_search, which all perform some form of searching. Also, ha_light_on/off and ha_service overlap, and run_tool is a generic catch-all that can execute many of the same operations provided by dedicated tools.
Most tool names follow a verb_noun pattern with domain prefixes (e.g., telegram_send, browser_navigate, spaces_list_buckets), but there are notable deviations like calendar_today, acc_log_missed, get_status, and run_tool. The mixture of domain-prefixed and non-prefixed names, along with occasional inverted patterns, creates mild inconsistency.
With 59 tools, the server is heavily overloaded, spanning multiple unrelated domains (Telegram, Obsidian, browser, Home Assistant, CRM, Zoho, Spaces, memory, docs). While the scope is broad, consolidating 59 tools into a single MCP server exceeds typical best practices and makes the surface difficult for agents to navigate.
Each sub-domain has some coverage (e.g., Telegram has send/read/typing/react/photo; browser has navigation/snapshot/click/type/evaluate), but there are notable gaps such as no delete operations for memory or Spaces, no edit for Telegram messages, and no note creation for Obsidian. The overall surface is broad but unevenly complete.