Skip to main content
Glama
prabhurajvardhan

Vibe Engineering MCP

by prabhurajvardhan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Vibe Engineering MCP

No user-submitted related servers found.

    Related Servers

    • agent-work-mcp

      yurikaza
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to run persistent, budgeted work sessions with dependency graphs, human decision queues, required validation, and clean handoffs for autonomous or human-in-the-loop execution.
      16
      MIT

    • agent-tasks

      keshrath
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables pipeline-driven task management for AI coding agents, with stage-gated workflows, dependency tracking, artifact versioning, and multi-agent collaboration.
      112 npm
      20
      MIT

    • AYA MCP

      sztlink
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables creative software agents to operate within bounded, temporary workcells, handling scored objectives through autonomous inspect, execute, capture, and correct loops while producing evidence-backed receipts for human review.
      Apache 2.0

    • odin

      Plazmodium
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a specification-driven workflow layer for AI-assisted coding, enabling agents to follow an explicit 11-phase feature workflow with checkpoints, artifacts, and quality gates.
      MIT

    • MangoMe

      tonnestate
      A
      license
      C
      quality
      B
      maintenance
      Persistent multi-agent work graph and document-state machine for contracts, specs, slices, evidence, verification, handoffs, and cost-aware AI execution.
      7
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have clearly distinct resource-action purposes, with prefixes and descriptions that separate tasks, git, repo, workspace, architecture, and verification concerns. Some overlap exists among status/context tools such as project_inspect, project_resume, workspace_status, and checkpoint_load, but their descriptions make the intended use reasonably clear.

    Naming Consistency5/5

    All tool names use consistent snake_case with predictable domain prefixes such as task_, git_, repo_, workspace_, architecture_, and checkpoint_. The verb/noun ordering is not perfectly uniform, but the convention is highly readable and consistent across the set.

    Tool Count3/5

    28 tools is heavy and exceeds the ideal 3-15 range for a single MCP server. The complex engineering lifecycle justifies many of them, but there is likely room to consolidate status/context tools, making the surface borderline rather than well-scoped.

    Completeness4/5

    The set covers the major lifecycle stages: project setup, requirements, architecture, task DAGs, workspaces, file operations, terminal execution, git, modules, contracts, integration verification, and checkpoints. Minor gaps include no explicit task_update/task_list, checkpoint_list, or workspace_cleanup, but agents can work around these through project_inspect and terminal_exec.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources