F
licenseA
qualityB
maintenanceEnables coding agents to track and coordinate project work through a shared SQLite ledger, including task plans, session ancestry, claims, work locations, blockers, and commits via MCP tools.
9
-
Vibecheck
by mgd34msu
Related Servers
Alternatives to Vibecheck
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP-capable coding agents to coordinate via authenticated task creation, claiming, messaging, and review approval over a secure local event log.-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.MIT
AgentTaskerofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, query, update, claim, hand off, and complete tasks on a local SQLite-backed, project-namespaced kanban board through stdio MCP tools, including filtering for ready/blocked/stale work and exchanging task attachments. It also lets agents list projects and manage statuses, ownership, and evidence without any server or accounts.MIT- AlicenseAqualityBmaintenanceMCP server for the nagi-ledger audit ledger and guardrail toolkit, exposing tools to record and annotate AI agent actions, subagent dispatches, and known dead ends, plus query session reports and statistics.8MIT
- FlicenseNot gradedqualityAmaintenanceA local-first MCP server and CLI that gives coding agents structured project memory, task contracts, context packs, backlog workflows, and verification evidence, storing data in reviewable Markdown/YAML with a fast SQLite index.4-
TDQS
A3.7/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct action within the plan/work lifecycle: joining a session, publishing/editing/acknowledging/reading plans, claiming/updating work, and viewing status/history. There is no genuine overlap that would cause an agent to select the wrong tool.
Naming Consistency4/5
Tool names consistently use lowercase snake_case with an object-first pattern (project_*, plan_*, work_*). Most names follow object_verb, though project_status and work_history are object_noun, creating a minor deviation.
Tool Count5/5
Nine tools is well-scoped for a coordination server covering session joining, plan management, work claiming/updating, and status/history queries. Each tool earns its place without redundancy or bloat.
Completeness4/5
The tool set covers the core plan and work lifecycle: publishing/reading/editing plans, acknowledging revisions, claiming and updating work, and querying status/history. Minor gaps exist, such as no explicit plan deletion or session leave, but agents can work around these in normal workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues