Skip to main content
Glama
cvandesande

project-code-intelligence

by cvandesande
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to project-code-intelligence

No user-submitted related servers found.

    Related Servers

    • codebase-memory-mcp

      DeusData
      A
      license
      A
      quality
      A
      maintenance
      High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 159 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.
      15
      43,043
      MIT

    • Sverklo

      sverklo
      A
      license
      A
      quality
      A
      maintenance
      Local-first code intelligence MCP server with hybrid BM25 + ONNX vector search, symbol-level impact analysis, diff-aware PR review with risk scoring, and persistent memory tied to git state.
      36
      64
      79
      MIT

    • leantoken

      morluto
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first code intelligence MCP server that enables coding agents to search code, inspect structure, read exact ranges, and explore Git history with explicit token budgets.
      23
      Apache 2.0

    • Context Zero Engine

      Classevelabs
      A
      license
      Not graded
      quality
      A
      maintenance
      A local code-intelligence engine for AI agents that indexes repositories into a PostgreSQL-backed code graph and serves structured, token-budgeted context over MCP and HTTP, enabling targeted queries on symbols, dependencies, contracts, and impact analysis.
      Apache 2.0

    • Graft

      amaar-mc
      A
      license
      B
      quality
      D
      maintenance
      Local-first codebase context engine that parses code into a ranked dependency graph and serves it to AI tools via MCP for deep structural understanding.
      5
      15
      1
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are mostly distinct in purpose: status overview, individual retrieval of records/findings/flow, semantic/text search, and graph relationships. However, 'get_code_intel_record' and 'related_code_intel' both involve records, but descriptions clarify the difference.

    Naming Consistency3/5

    Naming mixes patterns: 'get_code_intel_record' vs 'get_static_finding' (different ordering), 'search_code_intel_semantic' vs 'search_static_findings' (inconsistent prefix). 'code_intel_status' and 'related_code_intel' lack verb prefixes, breaking the verb_noun pattern.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a code intelligence server covering status, retrieval, search, and relationships. Neither sparse nor bloated.

    Completeness4/5

    Covers core needs: status, record/finding retrieval, two search modes, and graph edges. Missing explicit listing endpoints, but search can substitute. No clear dead ends for a read-only intelligence server.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources