Skip to main content
Glama
manik-prakash

narrow-mcp

by manik-prakash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to narrow-mcp

No user-submitted related servers found.

    Related Servers

    • siftr

      Bentlybro
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to quickly find relevant code, focus reads on important parts of large files, and pick relevant items from long lists, reducing token usage and search time.
      2
      MIT

    • gus

      SUD747
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to retrieve only the specific code sections that answer their questions, drastically reducing context usage while running fully locally.
      1
      MIT

    • Estelle

      uqeu
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent memory for coding agents and grounds their claims by verifying against the actual codebase, preventing hallucinated responses.
      506 npm
      Apache 2.0

    • skim-mcp

      helloderekg
      A
      license
      A
      quality
      C
      maintenance
      Token-efficient skim-then-expand I/O for agentic models, enabling lossless reading of large files via skeletons and exact expansion with anchor IDs.
      6
      MIT

    • Semantic Search MCP Server

      mix0z
      F
      license
      D
      quality
      D
      maintenance
      Enables AI agents to perform semantic search over codebases by converting natural language queries into efficient search patterns like grep and ripgrep. It utilizes LLMs to verify relevance and find code snippets that traditional keyword-based searches might miss.
      1
      -
    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.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of an agent selecting the wrong operation from this server. The tool's description also clearly delineates supported file types and explicitly excludes source files.

    Naming Consistency4/5

    The single name 'narrow_file' follows a clear verb_noun structure and is easy to predict. However, with only one tool there is no larger naming pattern to assess for consistency.

    Tool Count3/5

    A single tool is at the low end of what feels like a complete server, even though the server is intentionally narrow. The count is not a severe mismatch, but agents have no fallback or related operations available.

    Completeness5/5

    For the server's stated narrow purpose, the tool covers the entire workflow: it accepts a qualifying file and intent, returns verified verbatim relevant spans, and handles boundary cases by refusing source files. No obvious missing operation remains within this deliberately small scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources