DevProjex MCP Server
Related Servers
Alternatives to DevProjex MCP Server
- AlicenseNot gradedqualityAmaintenanceRepomix 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.60,348 npm28,896MIT
- AlicenseNot gradedqualityAmaintenanceA 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.dev7,725MIT
- AlicenseNot gradedqualityDmaintenanceGenerates optimized repository maps and enables identifier search with graph-ranking, designed for efficient LLM context caching and codebase navigation.1MIT
Related Servers
- FlicenseAqualityCmaintenanceA 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-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that provides AI agents with live, structured workspace awareness, including project listing, git status, and budgeted context packing, minimizing token usage.5 npm2MIT
- FlicenseAqualityBmaintenanceA 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-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives LLMs structured, read-only insight into local code repositories — directory tree, languages, dependencies, scripts, and config files.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- AlicenseNot gradedqualityDmaintenanceSecure multi-source MCP server for reading local, GitHub, GitLab, Bitbucket, and network source code with read-only-by-default access, enabling AI assistants to inspect repositories safely.1MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.