Skip to main content
Glama

Related Servers

Alternatives to DevProjex MCP Server

  • A
    license
    Not graded
    quality
    B
    maintenance
    Repomix MCP Server enables AI models to efficiently analyze codebases by packaging local or remote repositories into optimized single files, with intelligent compression via Tree-sitter to significantly reduce token usage while preserving code structure and essential signatures.
    116,149 npm
    29,203
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    A code ingestion tool that transforms your code into AI-optimized prompts instantly. Gather the relevant context with code2prompt under the hood. Learn more at code2prompt.dev
    7,752
    MIT

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    A read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.
    5
    ISC
  • A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to read and search code across many git repositories — files at any branch, tag or commit, history, diffs, blame and cross-repo search — over local paths or remote hosts like GitHub, GitLab and Bitbucket. It is read-only by construction, hiding secrets found in files and working with any MCP client over stdio or Streamable HTTP.
    1
    30 PyPI
    Apache 2.0
  • F
    license
    A
    quality
    B
    maintenance
    A read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.
    16
    -

TDQS

A4.4/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct action (list roots, tree structure, metrics, packaging, stored pack reads, text/symbol search, dependency analysis, file reads) and descriptions explicitly cross-reference when to use alternatives. No overlapping purpose causes misselection.

Naming Consistency4/5

Nearly all tools use snake_case verb_noun (list_projects, get_tree, pack_context, read_pack, search_project, get_file). Minor deviations: 'analyze' is a bare verb and 'related_files' is noun_plural, but convention remains predictable.

Tool Count5/5

Eight tools form a tight, well-scoped workflow for project context assembly, with each tool earning its place. No redundant or filler tools; count is ideal for the domain.

Completeness5/5

Surface covers listing projects, structure, metrics, packaging, stored result reads, text/symbol search, dependency analysis, and file reading. Complete for a read-only project-context server; no obvious lifecycle gaps.

Maintenance

ActivityActive
ResponsivenessLimited data