Codix Build MCP
Related Servers
Alternatives to Codix Build MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to perform software-development tasks such as deep research, codebase mapping, context curation, requirements and user-story generation, full-stack starter project scaffolding, and multi-step workflow execution.18 npmMIT
- FlicenseNot gradedqualityDmaintenanceTransforms AI coding assistants into context-aware developers by auto-detecting project context, remembering conversations, and executing commands safely with a multi-layer security model.-
- AlicenseNot gradedqualityBmaintenanceReduces token consumption for AI coding agents by 50-70% through intelligent code context filtering, Git delta tracking, and local SQLite/Tree-sitter indexing.167 npmMIT

nodespace-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to query a local knowledge base for persistent, searchable project context, reducing re-explanation and token usage.8Functional Source , Version 1.1, ALv2 Future- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to research topics, generate product requirements and user stories, map codebases, curate context, scaffold full-stack starter projects, and run multi-step development workflows.18 npmMIT
- AlicenseAqualityCmaintenanceProvides persistent memory and a codebase knowledge graph for AI coding assistants, enabling shared context across multiple tools like Claude, Cursor, and ChatGPT, with significant token reduction.518 npmMIT
TDQS
Scored across 16 tools
Each tool targets a distinct domain and output: project analysis, stack recommendation, architecture, templates, API generation, database schema, security, deployment, etc. Even the 'generate' tools are clearly differentiated by their object (prompt, API, docs). No two tools appear to do the same thing.
All tools share the codix prefix and lowercase dot-separated structure, but the second segment mixes verbs (analyze, get, generate) with nouns/adjectives (schema, checklist, guide, smart). This weakens the consistency of the verb_noun pattern, though it remains readable.
At 16 tools, the server is slightly above the typical 3-15 range, but the broad development lifecycle it covers justifies the count. The tools are not redundant, so the size feels reasonable rather than bloated.
The tool surface covers the major phases of a project build: analysis, stack, architecture, templates, API, database, security, docs, deploy, debug, marketplace, and cost optimization. Minor gaps exist, such as a dedicated testing tool or direct code scaffolding, but these can be worked around via the API test plan and template commands.