Skip to main content
Glama
LionTechSupport

MCQuest MCP

by LionTechSupport
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCQuest MCP

No user-submitted related servers found.

    Related Servers

    • Euthynos by euthynos-org

      Euthynosofficial

      euthynos-org
      A
      license
      Not graded
      quality
      B
      maintenance
      A local, read-only MCP server that provides AI coding agents with structural evidence about a repository, including dependency analysis and impact assessment, while naming the boundary of every answer without any LLM calls.
      52 npm
      Apache 2.0

    • Repiscope

      3xpr1ment
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that gives coding agents structured, read-only access to sibling repositories, ensuring security by design with zero write tools.
      MIT

    • TimeVerse Code Reader

      elimyliu
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for code reading with intelligent caching, line-range selection, and language detection, enabling AI assistants to efficiently and safely explore file systems.
      MIT

    • reflens

      cybertronayush
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that indexes reference repositories and provides tools for AI coding agents to retrieve lossless code context, enabling reasoning over codebases larger than the agent's context window.
      8
      2
      Apache 2.0

    • repo-context-mcp

      nduc99911
      A
      license
      A
      quality
      B
      maintenance
      MCP server that helps AI coding agents understand a repository by providing lightweight tree/map, code search, and token-budgeted context packing tools without dumping the entire monorepo into the prompt.
      3
      9 npm
      105
      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 16 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: listing files, reading files, searching code, finding imports, auditing patterns, and git status are all unambiguous. However, mcquest_project_context and mcquest_project_info significantly overlap — both serve as the first high-level project overview call — which introduces one notable source of confusion.

    Naming Consistency4/5

    All tools share the consistent mcquest_ prefix and use clean snake_case, making the set feel cohesive. Naming is not perfectly uniform because some tools follow action-based patterns like list_files or read_file, while others use noun-oriented names like project_context, phase_context, or find_evidence, but the overall pattern remains predictable.

    Tool Count4/5

    16 tools is slightly above the ideal 3–15 range, but the count is justified by a broad read-only investigative scope covering code, documentation, git state, phase evidence, and responsive-pattern auditing. The set feels reasonably sized rather than bloated, though a couple of closely related tools contribute to mild redundancy.

    Completeness5/5

    The tool surface thoroughly covers the domain of read-only project investigation: project orientation, file navigation, code search, dependency analysis, symbol usage, responsive audits, documentation exploration, phase comparisons, git context, and combined evidence lookup. There are no obvious dead ends or missing core operations within its stated read-only scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources