Nice Solutions

• Search Code — Locate monorepo code/docs by meaning (default K=12, monorepo project_root). Ladder: monorepo index_project first if empty; then search_code; hybrid_search only for explicit dense+keyword; community_patterns for lint catalogs; GitNexus MCP for callers/blast radius/rename. Does not expand to all projects unless search_all_projects=true.
• Ai Chat — Answer / explain / discuss after retrieval. For locate ("find", "where is code"), use search_code or hybrid_search first; GitNexus MCP for symbol impact. Uses Graph vs Hybrid routing for Q&A. PREFERRED for: "how does", "explain", "why", architecture discussion — after search when locations are known.
• Get Documents — Get list of indexed documents from the project. STRICT: Document structure is validated. Use verify_result tool to verify specific documents if needed.
• Upload Document — Upload single document file to Content Plane as canonical binary storage. Supports multiple file types: PDF, DOCX, MD, TXT, JSON, HTML, and media files. Routes via API Gateway → Content Service with resilience (retry, circuit breaker, timeout). PREFERRED for: capturing single files/documents without using legacy RAG binary upload doors.
• Inline Completion — Generate inline code completions at cursor position. Optimized for speed with lightweight models. Use for real-time code suggestions while typing. PREFERRED for: inline code completion, autocomplete, code suggestions.
• Generate Code — ALWAYS RECOMMENDED: Generate high-quality code with AI. Can include tests, documentation, and usage examples. Supports 7+ programming languages. PREFERRED for: "create", "generate", "write", "implement", "add", "build", code creation requests. Auto-triggers for: "create", "generate", "write", "implement", "add new", "build", code generation queries. STRICT: All generated code is automatically verified before returning. Use verify_result tool to double-check if needed.
• Code Review — Review code for quality, security, performance, and best practices. Provides actionable suggestions for improvement.
• Test Generate — Generate comprehensive test suite for existing code. Creates unit tests, integration tests, and test fixtures.
• Index Project — Index project files into RAG for semantic search. This scans the codebase and uploads to the vector database.
• Status Dashboard — View real-time MCP status including service health, index statistics, and recent documents.
• Get Current Context — Auto-detect file/function currently open in Cursor. Returns formatted context with code references. Helps understand current working context for precise communication.
• Generate Code Reference — Auto-format code references in standard format (startLine:endLine:filepath). Finds function/class boundaries and generates precise code references for communication clarity.
• Extract Error Context — Auto-extract context from error messages with advanced debugging. Parses error messages to find file paths, line numbers, error types, and suggests fixes based on similar patterns in codebase. Advanced: Includes execution tracing (call stack flow) and variable inspection (variable states at breakpoints) for step-through debugging.
• Suggest Examples — Find similar code examples/patterns from codebase. Uses semantic search to find code with similar functionality, then formats as code references for easy communication.
• Generate Communication Template — Auto-generate communication templates with full context. Combines get_current_context, generate_code_reference, and suggest_examples to create structured communication templates for precise AI interaction.
• Analyze Dependencies — Analyze file dependencies and relationships in codebase. Builds dependency graph showing imports, exports, and cross-file references for multi-file understanding. Includes pattern detection, security scanning, and flow analysis.
• Repository Graph Status — GitNexus static code graph status for the workspace (symbol graph, not runtime state). Best for dependency/refactor planning. Reads .gitnexus/meta.json when present and runs `gitnexus status`. Use status_dashboard first for runtime/API health evidence.
• Repository Graph Query — GitNexus query for execution-flow and dependency impact by concept. Use before refactors and architecture-impact changes. For runtime/API incidents, gather status_dashboard evidence first. Optional ingest_snapshot uploads result as .md to RAG.
• Watch Project — Watch project for file changes and auto-update index incrementally. Uses file system watcher to detect changes and update index in real-time.
• Analyze Diff — Analyze git diff to extract changed files, lines, and change types. Provides change impact analysis and suggests related updates.
• Verify Result — STRICT VERIFICATION: Verify that a claimed result is actually true. Prevents AI from fabricating success. Checks files, API responses, code generation, and operations. Always use this before claiming success.
• Refactor Code — Intelligent code refactoring with multi-file support. Analyze dependencies before refactoring to ensure safety. Supports rename, extract, move operations.
• Migrate Code — Migrate code between versions or frameworks. Uses MCP index to find migration patterns and analyzes dependencies for compatibility. Supports Python, TypeScript, JavaScript, and common frameworks.
• Detect Patterns — Detect code patterns, anti-patterns, code smells, security issues, and performance problems based on international standards (SonarQube, CodeQL, OWASP). Uses MCP index to find similar patterns and provide improvement suggestions.
• Standards Check — Check code against 9 coding standards: functional naming, no duplication, clean code, constants extracted, error handling standardized, logging integrated, validation centralized, business logic separation, type safety. Detects violations and provides actionable suggestions.

Showing the first 25 tools — full list and schemas: Directory API.