Skip to main content
Glama
Furkiozknn

local-notes-search-mcp

by Furkiozknn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to local-notes-search-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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

    • mcp-context

      ericlimabr
      F
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server that provides semantic search (RAG) over code repositories, enabling AI clients like Claude and Gemini to access project context without manual re-upload.
      -

    • vibe-hnindex

      AndyAnh174
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server to index your codebase once and search it across AI sessions with keyword, semantic, or hybrid search, keeping all data on disk.
      85 npm
      4
      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 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: index_directory ingests data, search_notes and ask_notes are differentiated as raw retrieval vs. LLM-synthesized answers, list_indexed_files provides observability, and remove_directory cleans up. Even the two retrieval-based tools are easy to tell apart because their outputs and purposes are explicit.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: index_directory, search_notes, list_indexed_files, ask_notes, remove_directory. There are no mixed conventions or vague generic verbs.

    Tool Count5/5

    Five tools is a well-scoped surface for a local notes search server: ingest, search, ask, list, and remove each earn their place. The count is neither bloated nor too thin.

    Completeness5/5

    The index lifecycle is fully covered: create/update via index_directory, read via search_notes and ask_notes, inspection via list_indexed_files, and deletion via remove_directory. Re-indexing handles changed and removed files, so there are no obvious dead ends or missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources