Smart Coding MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMART_CODING_VERBOSE | No | Enable detailed logging | false |
| SMART_CODING_BATCH_SIZE | No | Files to process in parallel | 100 |
| SMART_CODING_CHUNK_SIZE | No | Lines of code per chunk | 15 |
| SMART_CODING_MAX_RESULTS | No | Max search results | 5 |
| SMART_CODING_MAX_FILE_SIZE | No | Max file size in bytes (1MB) | 1048576 |
| SMART_CODING_SMART_INDEXING | No | Enable smart project detection | 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| a_semantic_searchA | Performs intelligent hybrid code search combining semantic understanding with exact text matching. Ideal for finding code by meaning (e.g., 'authentication logic', 'database queries') even with typos or variations. Returns the most relevant code snippets with file locations and line numbers. |
| b_index_codebaseA | Manually trigger a full reindex of the codebase. This will scan all files and update the embeddings cache. Useful after large code changes or if the index seems out of date. |
| c_clear_cacheA | Clears the embeddings cache, forcing a complete reindex on next search or manual index operation. Useful when encountering cache corruption or after major codebase changes. |
| d_check_last_versionA | Get the latest version of a library/package from its official registry. Supported ecosystems: npm (JS/TS), PyPI (Python), Packagist (PHP), Crates.io (Rust), Maven (Java/Kotlin), Go, RubyGems, NuGet (.NET), Hex (Elixir), CRAN (R), CPAN (Perl), pub.dev (Dart), Homebrew (macOS), Conda (Python/R), Clojars (Clojure), Hackage (Haskell), Julia, Swift PM, Chocolatey (Windows). Returns the version string to help you avoid using outdated dependencies. |
| e_set_workspaceA | Change the project workspace path at runtime. Use this when you detect the current workspace is incorrect or you need to switch to a different project directory. Creates cache folder automatically and optionally re-indexes the new workspace. |
| f_get_statusA | Get comprehensive status information about the Smart Coding MCP server. Returns version, workspace path, model configuration, indexing status, and cache information. Useful for understanding the current state of the semantic search system. |
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 6 tools
Most tools have distinct purposes, such as semantic search, indexing, cache management, dependency checking, workspace switching, and status retrieval. However, 'b_index_codebase' and 'c_clear_cache' could be confused since both relate to cache/index management, with overlapping use cases like handling major code changes.
The naming is inconsistent and chaotic, with no discernible pattern. Tools use prefixes like 'a_', 'b_', etc., which are arbitrary and not descriptive, mixed with descriptive names like 'set_workspace' and 'get_status'. This lack of a consistent verb_noun or other convention makes the set hard to navigate.
With 6 tools, the count is well-scoped and appropriate for a semantic coding assistant server. Each tool appears to earn its place by covering distinct aspects like search, indexing, cache, dependencies, workspace, and status, without being overly sparse or bloated.
The tool set covers core workflows for semantic code search and management, including search, indexing, cache handling, dependency updates, workspace switching, and status checks. A minor gap exists in lacking direct code manipulation tools (e.g., edit or refactor), but agents can likely work around this given the server's focus on search and analysis.