Skip to main content
Glama
doridoor

RepoMind-MCP

by doridoor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to RepoMind-MCP

No user-submitted related servers found.

    Related Servers

    • repo-cartographer

      builditwithgk
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that maps any repository into architecture diagrams, providing tools for scanning code facts, building import graphs, and generating Mermaid/DOT diagrams, plus architecture rule enforcement for CI.
      5
      31 npm
      1
      MIT

    • codegraph

      RexHung0302
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides tools to query a TypeScript/JavaScript/Vue codebase's dependency graph, enabling agents to find impacted files, hubs, orphans, and symbol relationships through natural language.
      248 npm
      MIT

    • javascript-mcp-server

      aferreiraguido
      A
      license
      C
      quality
      C
      maintenance
      Deterministic MCP server for semantic analysis of JavaScript/TypeScript codebases, including frameworks like Vue, Angular, React, and Node. It provides tools for type checking, code metrics, framework-specific analysis, and quality heuristics via static parsing.
      100
      1
      MIT

    • ast-impact-mapper-mcp

      vola-trebla
      A
      license
      A
      quality
      C
      maintenance
      MCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.
      15
      28 npm
      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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct phase of repository analysis: scanning structure, computing dependencies, generating diagrams, and calculating impact. No overlap or ambiguity exists between them.

    Naming Consistency5/5

    All tools follow the consistent pattern 'repomind_<verb>_<object>' with snake_case throughout. The verb-noun construction is uniform and predictable across the set.

    Tool Count5/5

    Four tools is an ideal size for a focused repository analysis server. Each tool earns its place and there is no bloat or redundancy.

    Completeness5/5

    The tool set forms a complete workflow: scan a workspace, extract dependencies, visualize them, and analyze impact. No obvious gaps exist for the stated purpose of repository analysis.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources