NSTOK AI Software Factory MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment (e.g., production) | production |
| ENABLE_AUDIT_LOG | No | Enable audit logging (true/false) | true |
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 |
|---|---|
| search_knowledgeC | Search across all NSTOK knowledge assets, features, UI components, DB entities, patterns, and repositories using hybrid search. |
| find_featuresB | Discover reusable business features from the NSTOK ecosystem (e.g. Nstok-feature-a, b, c) matching capabilities or keywords. |
| find_ui_componentsB | Find reusable design system UI components in Nstok-ui (DataTable, ProductTable, SearchInput, Button, etc.). |
| find_db_entitiesC | Search database schemas and entity definitions in Nstok-db (Product, Inventory, Sale, User, etc.). |
| find_existing_patternsC | Search established architectural patterns, code conventions, and guidelines in NSTOK. |
| get_project_contextC | Get full repository context, contained assets, and graph relationships for any NSTOK repo. |
| get_feature_contextA | Get deep-dive context for a specific feature, including capabilities, routes, UI/DB deps, and graph traversal. |
| get_app_contextB | Get full application architecture and composition details for a generated or production app. |
| analyze_prdB | Analyze a PRD text, extract required capabilities, match reusable vs missing assets, and compute reuse score. |
| create_app_planC | Generate a structured application implementation plan following the SEARCH -> REUSE -> ADAPT -> CREATE principle. |
| create_feature_planC | Generate a structured feature development plan scaffolded from Nstok-feature-template. |
| clone_app_templateB | Clone the standard baseline Nstok-app-template to initialize a new application workspace. |
| clone_feature_templateC | Clone the standard Nstok-feature-template to initialize a new feature repository. |
| add_feature_to_appB | Integrate and link an existing or newly created feature into an application workspace. |
| create_appC | Orchestrate end-to-end application generation from PRD, prioritizing feature reuse and template baselines. |
| create_featureB | Scaffold a new feature module from Nstok-feature-template when missing capabilities are required. |
| read_fileB | Safely read a file inside an NSTOK repository with audit logging and sandbox isolation. |
| write_fileB | Safely write or update a file inside an NSTOK repository with audit logging. |
| search_repo_codeC | Search for code snippets, symbol definitions, and text within an NSTOK repository. |
| git_statusB | Get git status, active branch, and modified files for a repository. |
| git_diffB | Inspect git diff in a repository before committing mutations. |
| create_branchC | Create a new feature branch (e.g. feature/ai/create-nstok-app-w) following NSTOK git workflow. |
| create_commitC | Create a structured git commit with a conventional commit message. |
| create_pull_requestB | Propose a Pull Request to main branch for human review and approval. |
| validate_architectureC | Validate that code obeys NSTOK architectural rules (UI-001, DB-001, ARCH-001, DEP-001). |
| run_testsC | Run unit and integration test suites in an isolated environment. |
| run_lintC | Run linting and static analysis on an NSTOK repository. |
| run_buildC | Run build and TypeScript type-checking for an application or feature. |
| update_knowledgeC | Feed newly generated application or feature metadata back into Nstok-knowledge-master. |
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 29 tools
Several tools have overlapping purposes: search_knowledge, find_features, find_ui_components, find_db_entities, find_existing_patterns, and search_repo_code all perform search-like operations. Similarly, create_app_plan and create_feature_plan both generate plans. However, descriptions provide some distinction through specific resource types and workflows.
Most tools follow a verb_noun pattern (e.g., search_knowledge, find_features, create_app_plan, clone_app_template). Minor deviations like get_project_context and run_tests are still readable and consistent with the pattern. Overall naming is predictable and consistent.
With 29 tools, the set is heavy and may overwhelm an agent. The high count is somewhat justified by the complex domain of software generation and knowledge management, but several tools appear redundant (e.g., multiple find_ tools, multiple create_plan tools), suggesting over-scoping.
The surface covers search, planning, creation, file operations, git workflow, validation, testing, and knowledge updating, which is comprehensive for a software factory. Minor gaps might include direct code editing tools or more granular git operations (e.g., merge, delete branch), but core workflows appear covered.