Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Required if EMBEDDING_PROVIDER is 'openai' | |
| EMBEDDING_PROVIDER | No | Embedding provider to use: 'openai' (fast, cloud) or 'transformers' (local, private) | transformers |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_codebase | Search the indexed codebase using natural language queries. Returns code summaries with file locations. Supports framework-specific queries and architectural layer filtering. Use the returned filePath with other tools to read complete file contents. |
| get_codebase_metadata | Get codebase metadata including framework information, dependencies, architecture patterns, and project statistics. |
| get_indexing_status | Get current indexing status: state, statistics, and progress. Use refresh_index to manually trigger re-indexing when needed. |
| refresh_index | Re-index the codebase. Supports full re-index or incremental mode. Use incrementalOnly=true to only process files changed since last index. |
| get_style_guide | Query style guide rules and architectural patterns from project documentation. |
| get_team_patterns | Get actionable team pattern recommendations based on codebase analysis. Returns consensus patterns for DI, state management, testing, library wrappers, etc. |
| get_component_usage | Find WHERE a library or component is used in the codebase. This is 'Find Usages' - returns all files that import a given package/module. Example: get_component_usage('@mycompany/utils') → shows all 34 files using it. |
| detect_circular_dependencies | Analyze the import graph to detect circular dependencies between files. Circular dependencies can cause initialization issues, tight coupling, and maintenance problems. Returns all detected cycles sorted by length (shorter cycles are often more problematic). |
| remember | 📝 CALL IMMEDIATELY when user explicitly asks to remember/record something. USER TRIGGERS: • "Remember this: [X]" • "Record this: [Y]" • "Save this for next time: [Z]" ⚠️ DO NOT call unless user explicitly requests it. HOW TO WRITE: • ONE convention per memory (if user lists 5 things, call this 5 times) • memory: 5-10 words (the specific rule) • reason: 1 sentence (why it matters) • Skip: one-time features, code examples, essays |
| get_memory | Retrieves team conventions, architectural decisions, and known gotchas. CALL BEFORE suggesting patterns, libraries, or architecture. Filters: category (tooling/architecture/testing/dependencies/conventions), type (convention/decision/gotcha), query (keyword search). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Codebase Intelligence | Automatic codebase context: libraries used, team patterns, and conventions. Read this BEFORE generating code to follow team standards. |