aisync
Related Servers
Alternatives to aisync
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server for AI coding agents that shares structured execution state, routes context deltas, and provides preflight nudges to prevent conflicts and stale decisions.MIT
- AlicenseBqualityBmaintenanceLets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.411MIT
- AlicenseAqualityDmaintenanceA local MCP server that enables multiple AI coding tools to share structured project state (decisions, tasks, bugs) so they coordinate without re-explaining.5MIT
- AlicenseBqualityAmaintenancerhizome-mcp is a local-first MCP server for task tracking and coordination of autonomous AI coding agents, providing crash-safe issue claiming, durable project memory, and dependency graphs using SQLite. It enables agents from different MCP-compatible clients to share a consistent view of project work with no accounts, Docker, or network dependency.351Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA shared memory and coordination server for multiple AI coding agents, built on the Model Context Protocol (MCP).6MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI coding tools to dispatch tasks in parallel to multiple installed AI CLIs with automatic failover, plus run multi-AI discussions and cross-reviews, hand code off between tools, manage shared workspaces, and inspect token usage, traffic, clients, and task memory. Also exposes image recognition (OCR/vision), tool and client administration, and log access through a single local hub.14 npmMIT
TDQS
Scored across 8 tools
Most tools have clearly distinct roles: claim/release form a clean pair, log writes, rules/rule_add read and write the rule layer, tidy surfaces proposals. The one fuzzy boundary is news vs status, both of which report on other agents' activity and recent events, so an agent may hesitate over which to call for a progress check.
All names are short, lowercase, and terse (claim, log, news, release, rules, status, tidy), giving a coherent house style. The only deviation is rule_add using a snake_case compound alongside the bare plural rules, which is a minor inconsistency rather than a pattern break.
Eight tools is tightly scoped to the coordination domain: two for claim lifecycle, two for awareness, three for the rule layer, one for journaling. Each tool maps to a distinct agent need with no filler.
Claim lifecycle, journaling, awareness, and rule creation are all covered, but the rule layer is write-once: there is no rule_update or rule_remove, and tidy only produces proposals with no tool to accept, reject, or apply them. Stale or duplicate rules can therefore be flagged but never resolved through the surface.