Skip to main content
Glama
pleibers

quick-search

by pleibers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to quick-search

No user-submitted related servers found.

    Related Servers

    • Repo Interrogator

      taggedzi
      A
      license
      A
      quality
      C
      maintenance
      A local-first MCP server that enables AI tools to safely inspect and search code repositories, providing indexing, deterministic BM25 search, code outlining, and context bundles without code modification.
      9
      1
      MIT

    • fastcontext_explore

      LIVELUCKY
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that wraps Microsoft's FastContext as a read-only repository exploration subagent, enabling coding agents to delegate broad code searches and receive compact file:line citations.
      1
      1
      MIT

    • code_nav MCP

      ARQAWA
      F
      license
      B
      quality
      D
      maintenance
      Deterministic code navigation MCP server for Codex/CodeCLI that provides compact repo context using git-aware deterministic search tools without semantic search or embeddings.
      8
      -
    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.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: one performs broad repository search with bounded snippets, the other expands specific results into full context. The descriptions explicitly state when to use the second tool only after the first, leaving no ambiguity.

    Naming Consistency5/5

    Both names follow the same `search_` prefix pattern with a modifier distinguishing scope: `_repo_context` for broad search and `_focused_context` for targeted expansion. This is a consistent and predictable convention.

    Tool Count4/5

    With only two tools, the server feels minimal, but the narrow purpose of a quick-search utility is well served by this two-stage design. The count is slightly thin yet not unreasonable for the stated scope.

    Completeness4/5

    The tool surface covers the full intended workflow: initial bounded search, then optional expansion for deeper context. No obvious dead ends exist, though more advanced query refinement or result-management features could be considered minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources