iranti
Related Servers
Alternatives to iranti
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceProvides persistent, local-first memory with knowledge graph and hybrid search for AI coding agents, reducing token usage by storing decisions, patterns, and codebase context.8-
- AlicenseAqualityBmaintenanceProvides persistent, searchable memory across AI coding agent and chat history (Claude Code, Codex, Gemini CLI, ChatGPT, and more) via retrieval-augmented generation, enabling semantic and hybrid search to retain context across sessions.5MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with persistent, graph-connected memory across projects, enabling cross-project context retrieval via synaptic connections and hybrid search.6 npm8MIT
- AlicenseNot gradedqualityBmaintenancePersistent memory for AI coding agents that stores and recalls preferences, decisions, and conventions via semantic similarity, with zero cloud dependencies and plug-and-play MCP integration for Claude Code.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.MIT
- AlicenseNot gradedqualityDmaintenanceProvides long-term memory for AI coding agents, enabling them to remember, search, and organize information across sessions and platforms like Claude Code, ChatGPT, and Cursor.14 npm8MIT
TDQS
Scored across 16 tools
Most tools have distinct purposes, but there is some overlap between iranti_observe and iranti_search (both retrieve facts) and between iranti_write and iranti_write_issue/iranti_write_rule (all write facts). The descriptions clarify differences, but an agent might initially confuse these pairs.
All tools follow a consistent iranti_verb or iranti_verb_noun pattern, using snake_case throughout. The naming is highly predictable, with clear prefixes and descriptive suffixes.
16 tools is slightly high but reasonable for a memory management system, covering handshake, checkpointing, querying, writing, and history. It might feel heavy, but each tool appears to serve a specific role in the workflow.
The toolset provides comprehensive coverage for memory operations: initialization (handshake), per-turn checks (attend), CRUD operations (write, query, search), history (history), relationships (relate, related), and specialized writes (issue, rule). No obvious gaps exist for the domain.