Codix Build MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODIX_BUILD_API_KEY | No | API key to enable higher quota tier and cloud-hosted templates registry | |
| CODIX_BUILD_TOKEN_BUDGET | No | Token budget per step for Smart Context Mode |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codix.project.analyzeB | Analyze a short project brief into type, modules, risks, milestones and Smart Context chunks. |
| codix.stack.recommendC | Recommend a stack from project type, budget, team level and hosting target. |
| codix.prompt.generateB | Generate a compact agent prompt using Smart Context Mode instead of long pasted docs. |
| codix.architecture.getB | Return the canonical architecture layers and build order for a project type and stack. |
| codix.template.getA | Return a project template file tree, commands and notes for Laravel, Next.js, Flutter, WordPress, API, docs and more. |
| codix.license.injectB | Generate Codinfy-compatible license integration instructions without hardcoding secrets. |
| codix.design.applyC | Apply a pragmatic design system: tokens, components and app-like mobile UX rules. |
| codix.api.generateC | Generate API route/controller/service/validation/test plan from resources. |
| codix.database.schemaC | Generate database schema guidance: migrations, relations and seeders. |
| codix.security.checklistC | Return a security checklist for stack, features and compliance needs. |
| codix.marketplace.checkB | Check readiness for Codinfy Store / CodeCanyon packaging. |
| codix.docs.generateC | Generate documentation outline and starter snippets. |
| codix.deploy.guideB | Generate deployment steps for cPanel, VPS, Docker, Vercel, Render, Railway, Cloudflare Pages, Firebase, Supabase or app stores. |
| codix.debug.helpB | Map an error message to likely causes and verification commands. |
| codix.cost.optimizeC | Suggest prompt-token and infrastructure cost optimizations. |
| codix.context.smartC | Smart Context Mode: return only the context chunks needed for the active task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.