Skip to main content
Glama
amalikn

smart-coding-mcp

by amalikn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to smart-coding-mcp

No user-submitted related servers found.

    Related Servers

    • ContextTree MCP

      chelslava
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding assistants to perform local semantic code search using AST parsing and embeddings, finding code by meaning with exact file and line locations, plus AST-based usage lookup.
      4
      MIT

    • Smart Coding MCP

      omar-haris
      A
      license
      A
      quality
      F
      maintenance
      Provides intelligent semantic code search using local AI embeddings, enabling natural language queries to find relevant code by meaning rather than exact keywords. Indexes codebases in the background with smart project detection and privacy-first local processing.
      6
      9 npm
      200
      MIT

    • code-search-mcp

      genautkin
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to semantically search codebases by meaning rather than exact text, with zero external daemons and fully local embeddings. Works out-of-the-box with Claude Code, Gemini CLI, Antigravity, and Cursor.
      4
      MIT

    • CodeGrok MCP

      dondetir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic code search for AI assistants by indexing codebases with embeddings and Tree-sitter, returning relevant snippets via natural language queries.
      15
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a clearly described purpose and most are easy to distinguish. The main ambiguity is between b_index_codebase and c_clear_cache, since both can result in a rebuilt embedding index, but their described triggers differ enough to avoid serious confusion.

    Naming Consistency3/5

    The names use consistent snake_case and mostly follow a verb_noun pattern, but the arbitrary a_, b_, c_ prefixes are not semantically meaningful and a_semantic_search breaks the verb_noun pattern by leading with an adjective. The overall style is readable but mixes conventions.

    Tool Count4/5

    Six tools is a reasonable size for a focused semantic code search server. However, d_check_last_version is unrelated to the core semantic-search/indexing workflow, so the tool set is slightly less focused than it could be.

    Completeness4/5

    The core workflow is well covered: workspace setup, indexing, cache invalidation, semantic search, and server status. Minor gaps exist around configuration control or more granular index inspection, but agents can complete the primary tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources