Skip to main content
Glama
Lianye-Scythe

scythe-context-mcp

by Lianye-Scythe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to scythe-context-mcp

No user-submitted related servers found.

    Related Servers

    • Solumbe

      BASHBOP
      A
      license
      A
      quality
      A
      maintenance
      Local-first code context CLI + MCP server: discover, index, and search repos; generate task-aware context packs, code maps, agent harnesses, and PR-review/merge-readiness gates for coding agents and reviewers.
      4
      14
      1,390 npm
      2
      MIT

    • code-memory-rs

      juandisay
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables local semantic code search across repositories using natural language, with AST-aware chunking and hybrid vector/FTS5 retrieval.
      -

    • 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
      19 npm
      1
      MIT

    • dnomia-knowledge

      ceaksan
      A
      license
      A
      quality
      C
      maintenance
      Local knowledge engine for codebases with hybrid search, knowledge graph, and interaction tracking, enabling Claude Code to search and interact with project knowledge locally.
      7
      2
      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

    B3/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools have distinct purposes, but repo_semantic_search and repo_context_pack overlap in functionality, potentially causing confusion. repo_doctor and repo_index_status both address diagnostics but at different granularities, adding mild ambiguity.

    Naming Consistency2/5

    The majority of tools follow a 'repo_' prefix, but one tool (gemini_embedding_probe) breaks this pattern. Additionally, verb-based names (doctor, reindex) mix with noun-based names (index_status, related_files, context_pack, semantic_search), creating inconsistency.

    Tool Count5/5

    With 7 tools, the server covers the core operations for context management without being overwhelming. Each tool addresses a specific need, making the count well-scoped for the domain.

    Completeness4/5

    The tool set covers diagnostics, indexing, related file exploration, and search, which are the primary tasks. Missing a tool for configuration management or indexing reset is a minor gap, but the core workflow is supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources