Skip to main content
Glama
SammySnake-d

Fast Context MCP

by SammySnake-d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Fast Context MCP

No user-submitted related servers found.

    Related Servers

    • Fast Context MCP

      TripQi
      A
      license
      A
      quality
      D
      maintenance
      Enables AI-driven semantic code search using Windsurf's reverse-engineered SWE-grep protocol to query local codebases with natural language. It executes local search tools like ripgrep and tree-node-cli to return relevant file paths and line ranges to MCP-compatible clients.
      2
      149
      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.
      15
      1
      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
      -

    • VecGrep

      VecGrep
      A
      license
      A
      quality
      C
      maintenance
      Semantic code search MCP server that reduces token usage by ~95% by returning top relevant code chunks instead of full files.
      8
      9
      MIT

    • local-notes-search-mcp

      Furkiozknn
      -
      license
      Not graded
      quality
      Not graded
      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.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one extracts an API key from a local installation, the other performs semantic code search. No overlap or ambiguity exists.

    Naming Consistency4/5

    Both tools use snake_case and follow a descriptive pattern (extract_* and fast_*). Although the verb style differs slightly (command vs. brand adjective), the naming is clear and consistent in format.

    Tool Count3/5

    With only two tools, the server feels minimal. While the tools are focused, the count is on the low end of what is typically expected, making it borderline appropriate.

    Completeness2/5

    The server covers API key extraction and semantic search, but lacks related operations like API key management, file content retrieval, or result navigation. Significant gaps exist for a context-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources