Skip to main content
Glama
Baktun-Studio

com.linebreakapp/linebreak-gate

by Baktun-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to com.linebreakapp/linebreak-gate

No user-submitted related servers found.

    Related Servers

    • backlog-mcp

      corbym
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files that live inside your project repository. There is no shared server. The backlog files live in your repo under requirements/, committed and versioned alongside your code
      16
      3
      -
    • serenedge by SerenEdge

      serenedgeofficial

      SerenEdge
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to claim, work, and submit tasks on SerenEdge projects by exposing the platform's agent API as MCP tools.
      MIT

    • devcontract

      maazbin
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve cited git-history explanations for files and tickets, compile a Team Engineering Contract from repository artifacts, and follow guided Understand/Build workflows over MCP stdio. It lets clients such as Grok, Claude Code, Codex, Kiro, and Cursor share the same tools for evidence-backed repository understanding.
      1
      153 npm
      Apache 2.0

    • greenroom-mcp

      igility
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects AI coding agents to Greenroom's per-story Storybook reviews, allowing them to list feedback with screenshots, reply to threads, mark stories addressed, and approve stories when explicitly delegated.
      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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct function: listing stories, picking the next one, retrieving full story details, updating status, checking acceptance criteria, and inspecting spec status. There is no overlap in purpose, making selection unambiguous.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (list_stories, get_story, set_story_status, check_story), but 'next_story' and 'spec_status' deviate from this pattern. Still, all names are readable and consistent in style (lowercase underscores), with only minor deviations.

    Tool Count5/5

    Six tools is well within the ideal range and each tool earns its place, covering the core lifecycle of story selection, status updates, and gate verification without redundancy.

    Completeness5/5

    The set covers the entire local workflow: enumerate stories, pick next, get full details, update status, run acceptance checks, and verify spec approval. No obvious dead ends or missing operations for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources