Skip to main content
Glama
mgd34msu

Vibecheck

by mgd34msu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Vibecheck

No user-submitted related servers found.

    Related Servers

    • vibecheck

      mgd34msu
      F
      license
      A
      quality
      B
      maintenance
      Enables 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
      -
    • agentbus by RetentionSoftware

      agentbusofficial

      RetentionSoftware
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets parallel coding sessions in one repository coordinate, by registering agents with roles and statuses, delivering messages directly into their context, tracking tasks with dependencies, and claiming file paths to detect conflicts. It runs as a single loopback-only Python process backed by SQLite, with no accounts or external services.
      MIT

    • Synapse MCP

      holaluiz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to work concurrently on the same repository by coordinating task ownership, file locks, architectural decisions, investigation gaps, handoffs, and audit activity through a local SQLite-backed MCP interface.
      5 npm
      MIT

    • Morion AI MCP

      miksushko
      A
      license
      Not graded
      quality
      B
      maintenance
      Local kanban board & harness for coding agents over MCP: agents claim and move tasks, read and write notes, and build Auto-code workflows, within per-folder permissions and an audit log.
      4 npm
      1
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources