Ruflo GPT
Related Servers
Alternatives to Ruflo GPT
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceGives every AI agent on a machine a shared, local-first long-term memory: 16 tools to save, search, edit and organize structured notes in one SQLite file, with attribution per client. Runs over stdio or localhost HTTP, so Claude Code, omp and any other MCP client recall the same facts, decisions and entities.16MIT
- AlicenseNot gradedqualityBmaintenanceEnables development agents to keep persistent memory: proposing and reviewing workspace-scoped content, running hybrid search over accepted sources, and resuming projects with auditable history and provenance. It exposes 32 MCP tools over stdio and authenticated Streamable HTTP, with optional embeddings and rerank.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store, search, and recall persistent project and cross-project memories locally over MCP, keeping architectural decisions, conventions, and error patterns available across sessions. Also optionally exposes a task server for autonomous task execution driven by that same memory store.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search, record, correct, and review the provenance and version history of memories, and to obtain answers composed from guarded context in which private values are replaced by placeholders and resolved locally on the device. Exposes these capabilities through dependency-free tools over stdio.MIT
- AlicenseAqualityAmaintenanceProvides AI coding tools with one local SQLite memory and rules store they can read over MCP, REST or the CLI, so facts, sessions and goals persist across sessions and shared rules are written into each tool's own instruction file. Runs entirely on your machine with no account, telemetry or network calls by default.4132,159 npm9Apache 2.0
- AlicenseBqualityDmaintenanceLocal Markdown-backed memory tools for Codex and other MCP-capable agents. Exposes durable agent knowledge via CLI and MCP server.5MIT
TDQS
Scored across 16 tools
The memory tools are clearly differentiated by operation (store, retrieve, search, delete, list, stats), but the task tools have overlapping boundaries. task_status, task_summary, and task_list are easy to confuse, as are task_update, task_assign, task_complete, task_cancel, and task_retry. The repetitive templated descriptions provide little help in distinguishing these task operations.
All tool names use consistent snake_case with clear resource prefixes: memory_* and task_* for their domains. codex_status is a minor deviation from the verb_noun pattern but still fits the overall resource_action convention.
Sixteen tools across two substantial domains (persistent memory and task tracking) plus adapter status is reasonable, though the nine task tools feel slightly over-granular for metadata-only operations. The count is not excessive but is near the upper end of a well-scoped set.
The memory surface covers storing, retrieving, searching, deleting, listing, and stats, while the task surface covers creation, updates, status, listing, completion, cancellation, retry, assignment, and summary. Together with codex_status, this provides full lifecycle coverage for the stated domain with no obvious dead ends.