Skip to main content
Glama
lorenzo-cambiaghi

lynx-mcp

by lorenzo-cambiaghi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lynx-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-local-rag

      damoqiongqiu
      A
      license
      A
      quality
      A
      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
      79 npm
      13
      MIT

    • rag-mcp

      MasihMoafi
      A
      license
      Not graded
      quality
      B
      maintenance
      A local hybrid-search MCP server that enables coding agents to query files and folders using natural language, returning relevant code chunks with exact source paths. Everything runs on-device with no API keys or network calls.
      5
      MIT

    • Code Memory

      kapillamba4
      A
      license
      A
      quality
      D
      maintenance
      MCP server with local vector search for your codebase. Smart indexing, semantic search, Git history — all offline.
      7
      75 PyPI
      49
      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.
      5
      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

    A4.3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Tools mostly have distinct purposes, and the descriptions explicitly cross-reference when to use one versus another (e.g., find_usages vs impact vs describe_symbol). Some overlap exists between search, find_similar, and deep_search, but their scopes are clearly differentiated enough for an agent to select correctly.

    Naming Consistency3/5

    Most names use snake_case, but the pattern is inconsistent: some are verb_noun (find_definition, list_sources), some are noun phrases (repo_overview, module_summary), and a few are single words (impact, feedback). This mixed style reduces predictability.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 range, but the breadth is justified by combining code navigation, semantic search, graph queries, and RAG index management. The count feels reasonable rather than bloated.

    Completeness5/5

    The toolset covers the full code understanding workflow: overview, definition, usages, tests, impact, similar code, symbol/module summaries, graph export, search variants, and index lifecycle management. No obvious gaps prevent an agent from accomplishing common navigation and search tasks.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources