Skip to main content
Glama
Sign In
rebuild-dossier

rebuild-dossier

by Parker-Fawcett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to rebuild-dossier

No user-submitted related servers found.

    Related Servers

    • cc-agent

      Gonzih
      A
      license
      A
      quality
      D
      maintenance
      MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
      47
      44 npm
      2
      Apache 2.0

    • mcp-flow

      remimenguy
      A
      license
      A
      quality
      D
      maintenance
      A safe, local MCP server that lets Claude drive a controlled software-development loop (inspect, read, plan, patch, apply, check, analyze, fix, summarize) on a project, using deterministic tools and real diffs/test runs.
      10
      1
      MIT

    • sove-mcp

      JrKrishh
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives Claude structural understanding of a codebase—dependency graph, entry points, complexity ranking, and import cycles—without reading every file into context.
      4
      MIT
    • reforge-mcp

      reforge-mcp

      Codewithaiyan
      A
      license
      A
      quality
      B
      maintenance
      Helps Claude Code clean up messy repositories: find dead code, duplicate logic, oversized files, and circular dependencies, then apply fixes with optional tests and rollback.
      10
      3,826 PyPI
      2
      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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct role in the pipeline: ingesting, crawling, flagging bugs, reading/resolving cases, and generating the final spec. No two tools appear to perform the same action.

    Naming Consistency5/5

    All tool names follow the consistent verb_noun snake_case pattern (crawl_site, ingest_repo, resolve_case, etc.), making the set predictable and easy to navigate.

    Tool Count5/5

    Six tools is a well-scoped number for a multi-stage rebuild workflow. Every tool maps to a distinct step in the process, and none feel redundant or extraneous.

    Completeness4/5

    The workflow appears complete from ingestion through case resolution to spec generation. The only minor gap is that there is no explicit tool to trigger reconciliation or auto-resolution, which seems to happen implicitly or externally.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources