Skip to main content
Glama
Sign In
Vibecheck

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
      -
    • MileStack

      MileStack

      SuperYang006
      A
      license
      A
      quality
      B
      maintenance
      Local-first task and progress database shared by developers and coding agents. Agents claim ready tasks over MCP, record progress and handoffs,and submit commits for independent review; developers confirm, prioritize, and approve work in a local web dashboard. Data stays in a SQLite file inside your project, with no cloud service or account required.
      15
      309 npm
      11
      Apache 2.0
    • agentbus

      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
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.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

    ActivityStale
    ResponsivenessNo recent community issues

    Resources