Crabrix
Related Servers
Alternatives to Crabrix
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.53 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLets AI agents create, read, update, and restore client-side encrypted shared workspaces and artifacts that other agents and people can open through a single link. Writes are version-guarded to prevent clobbering, and content is deleted 24 hours after the last edit.19 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, read, update, list, restore and share encrypted workspaces and artifacts through a single link that people and other agents can open. Content is encrypted client-side and auto-deleted 24 hours after the last write, with version-checked writes that prevent agents from overwriting each other.19 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, read, update, list, restore and version-share encrypted workspaces of files and context, so multiple agents and people can collaborate on one link that self-deletes 24 hours after the last edit.19 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, read, update, restore, and share encrypted workspaces and artifacts through a single link that both people and other agents can open and edit. Writes are version-checked to prevent clobbering, and content is deleted 24 hours after the last edit.19 npmMIT
- AlicenseNot gradedqualityAmaintenanceLets agents create, read, update, list, and restore shared encrypted workspaces and artifacts, exchanging a single link that both people and other AI agents can open and edit. Content is encrypted client-side with version-checked writes, so concurrent writers can't silently clobber each other and links can be shared as read-only or editable.19 npmMIT
TDQS
Scored across 18 tools
The core room/file tools are reasonably distinct (create vs connect vs status vs read_file vs handoff), but the runtime subset overlaps heavily: crabrix_runtime_inspect and crabrix_runtime_job both read status/output, and Stop appears in both runtime_job and runtime_control. Similarly crabrix_apply_changes, crabrix_apply_operations, and crabrix_plan_changes share the same 'apply changes' space, leaving boundaries that require careful description reading to separate.
The crabrix_ prefix is consistent, but the second component mixes conventions: single verbs (connect, select, create, disconnect), verb_noun (plan_changes, apply_operations, end_room, read_file, apply_changes), nouns (snapshot, status, handoff, runtime_clients, runtime_job), and noun_verb (runtime_inspect, runtime_request, runtime_start). The runtime_* grouping partially helps but still mixes noun and verb forms within it.
At 18 tools the surface is on the heavy, borderline side (16-25 band), and the runtime subdomain alone consumes six tools for what could arguably be consolidated. The domain is genuinely complex (rooms, editing, execution), so most tools earn a place, but some runtime reads appear redundant.
The lifecycle is largely covered: room creation/join/leave/close, sharing/links, status/snapshot/file reads, selection, atomic edits plus plan/apply with recovery, and a full runtime request-to-inspect pipeline. Minor gaps like a dedicated file listing or multi-file batch read are workable via status/snapshot, so agents are unlikely to hit dead ends.