Skip to main content
Glama
TripQi

Fast Context MCP

by TripQi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Fast Context MCP

No user-submitted related servers found.

    Related Servers

    • Fast Context MCP

      SammySnake-d
      A
      license
      A
      quality
      A
      maintenance
      Enables AI-driven semantic code search by leveraging Windsurf's reverse-engineered protocol to perform multi-round local searches using natural language. It automatically executes bundled ripgrep and file operations to return relevant code snippets and file paths to MCP-compatible clients.
      2
      165 npm
      363
      MIT

    • local-notes-search-mcp

      Furkiozknn
      A
      license
      A
      quality
      B
      maintenance
      Enables natural-language semantic search over your own local files through an MCP server, fully offline without API keys or a server daemon, with optional LLM-grounded answers and exact file:line sources.
      5
      MIT

    • code-search

      RaziStuff
      A
      license
      Not graded
      quality
      B
      maintenance
      Semantic + lexical code search as an MCP server. Agents query in natural language and get back ranked file:line ranges to read precisely.
      8 npm
      1
      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

    • code-rag

      kkuppula
      F
      license
      Not graded
      quality
      C
      maintenance
      A semantic code search MCP server that enables natural language queries against your codebase, supporting features like related file discovery and context expansion, all running locally.
      2
      -
    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 2 tools

    Disambiguation5/5

    The two tools serve completely distinct purposes: one performs AI-powered code search, and the other extracts an API key. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both tools use snake_case and follow a descriptive noun-verb pattern (fast_context_search, extract_windsurf_key). The naming is mostly consistent, though one is more of an adjective_noun_verb while the other is a clear verb_noun.

    Tool Count3/5

    With only two tools, the server feels thin for its purpose. However, it is narrowly focused on AI-driven search, and each tool is substantial, so the count is borderline acceptable.

    Completeness4/5

    The core search workflow is covered by the search tool, which includes configurable parameters for depth and turns. The key extraction is a necessary setup step. There are no obvious dead ends, though a few extra utilities (e.g., search history or config management) could enhance completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources