Skip to main content
Glama
Codix Build MCP

Codix Build MCP

by bakalagoin

Related Servers

Alternatives to Codix Build MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to query a local knowledge base for persistent, searchable project context, reducing re-explanation and token usage.
      8
      Functional Source , Version 1.1, ALv2 Future
    • A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      5
      18 npm
      MIT

    TDQS

    B3/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.