Skip to main content
Glama
Sign In
nexus-mcp-ci

nexus-mcp-ci

by jaggernaut007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nexus-mcp-ci

Related Servers

  • codebase-memory

    H-Gelender
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for local codebase memory: semantic indexing, hybrid search, and clean code analysis (static + LLM) with retrievable project notes, designed to run fully local on modest hardware.
    MIT

  • codesteer-atlas

    LuisCarlosLopes
    A
    license
    A
    quality
    A
    maintenance
    Local MCP server for semantic code search using Tree-sitter AST parsing, local embeddings, and hybrid search; enables indexing and querying codebases entirely offline.
    7
    MIT

  • mcp-local-rag

    damoqiongqiu
    A
    license
    A
    quality
    C
    maintenance
    A fully local RAG MCP server for semantic code search and code intelligence, using AST-level chunking and hybrid search to pinpoint functions, classes, and APIs. No cloud, no API keys, zero setup.
    16
    155 npm
    13
    MIT

  • cba

    davidgeorgehope
    F
    license
    Not graded
    quality
    C
    maintenance
    MCP server for semantic code search and explanation. Allows AI agents to search, ask questions, and manage memory about a codebase with local embeddings and LLM integration.
    -
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.3/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct facet of code intelligence: status vs index (state vs build), search vs find_symbol (semantic vs name lookup), graph (call relations), analyze (quality), map (overview), memory (notes). Descriptions explicitly cross-reference each other to steer selection, leaving no real overlap.

Naming Consistency4/5

Names are consistently short, lowercase single tokens, but they mix noun-style (status, graph, map, memory) with verb-style (index, search, analyze) and one snake_case outlier (find_symbol). Mostly predictable, minor deviations only.

Tool Count5/5

Eight tools is well-scoped for a code-index server, and each earns its place with a clear, non-redundant role spanning indexing, search, navigation, analysis and memory.

Completeness5/5

Covers the full lifecycle: index status/build, semantic and name search, call-graph tracing, quality analysis, architectural overview, and persistent project memory. Literal grep is delegated to built-ins, which is a reasonable boundary, leaving no notable gaps.

Maintenance

ActivityActive
ResponsivenessSlow

Resources