Skip to main content
Glama
jack-whimvy

vibecompass-mcp

by jack-whimvy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to vibecompass-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-vibekanban

      yigitkonur
      A
      license
      A
      quality
      D
      maintenance
      MCP server that bridges AI coding assistants to Vibe Kanban, enabling task, session, and queue management without leaving the coding environment.
      12
      3 npm
      5
      MIT

    • kb

      okash1n
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that provides a shared context and learning foundation across multiple AI tools (Claude, Copilot, Codex) for multiple projects, enabling persistent knowledge, decisions, and gap reflection through note storage.
      MIT

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      123 npm
      5
      MIT
    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

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool targets a distinct purpose: session summary, conflict management, decision logging, feature/file/project context, proposals, and status updates. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a clear verb_noun pattern (e.g., get_feature_context, log_decision) using snake_case, making them predictable and easy to navigate.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a project context server. It covers session handling, conflicts, decisions, features, files, proposals, and status without being too numerous or sparse.

    Completeness5/5

    The tool surface covers the full lifecycle for project context: reading current state (get_project_context, get_feature_context, get_file_context, get_conflicts, get_decision_log, list_pending_proposals) and updating it (add_session_summary, flag_conflict, log_decision, update_feature_status). No obvious gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources