CollabMCP
Related Servers
Alternatives to CollabMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceShared context for multiple Claude Code sessions working on the same project.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a shared, repo-local memory that lets coding agents recall relevant decisions, conventions, gotchas, and open threads, save new entries, coordinate file claims, and cache file summaries across tools and sessions.88 npmMIT
- AlicenseAqualityBmaintenanceEnables teams to share structured, git-synced context among AI coding agents working on the same repository, including living plans, task declarations, handoff briefs, file-provenance history, and conflict detection.1220 npm3MIT
- AlicenseCqualityBmaintenanceEnables Claude Code agents and sub-agents to share a persistent, compiled memory of project state, decisions, tasks, and facts across sessions instead of re-reading transcripts. Provides token-efficient bootstrap, search, commit, leased task claiming, and task-specific context compilation so parallel agents can coordinate without clobbering each other.58 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent codebase memory for Claude Code, enabling semantic understanding of the project structure and action history across sessions to reduce redundant file reads.1MIT
- AlicenseAqualityBmaintenanceProvides agent coordination for Claude Code through a shared blackboard, decision tracking with rationale, and local semantic search over git-trackable JSONL files. It enables users to assemble tailored context packages and manage a lightweight knowledge graph for complex development tasks.1552 npm7MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: broadcast for messaging, get_session for context snapshot, recall for reading past decisions, remember for writing decisions, who_owns for ownership queries. No overlap.
Naming is mixed: 'broadcast', 'recall', 'remember' are single verbs; 'get_session' is verb_noun; 'who_owns' is a question. No consistent pattern, though all are readable.
With 5 tools covering communication, session management, knowledge base, and ownership, the count is well-scoped for a team collaboration server.
Covers key collaboration features (messaging, context, decisions, ownership). Minor gap: no explicit lock acquisition/release tool, but get_session and who_owns may suffice.