Skip to main content
Glama
syaryn
by syaryn

Related Servers

Alternatives to mcp-jp-fts

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables fast, low-token code search for AI coding agents via a local BM25 engine built on SQLite FTS5, with support for camelCase, snake_case, and Japanese text. Provides a stateless MCP stdio server and a Hermes adapter for multi-agent environments.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides local semantic search over files using embeddings, enabling directory indexing and natural language queries without external services.
      17 PyPI
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables local semantic code search across repositories using natural language, with AST-aware chunking and hybrid vector/FTS5 retrieval.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables lexical search over local Markdown wiki folders using SQLite FTS5, with MCP tools for querying and managing wiki indices.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Provides fast, token-efficient search over coding agent documentation (e.g., Claude Code, Cursor) using local SQLite FTS5 indexing, with tools for searching snippets, reading pages, and grepping markdown.
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Turns a local folder of documents into a queryable index that an LLM agent can pull from on demand, keeping only a compact table of contents in context. Exposes five tools (index, search, read, grep, neighbours) over a single offline SQLite FTS5 store so the model retrieves exact, citable sections instead of being handed whole files.
      MIT

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct purpose: delete, stats, index directory, list files, search, update single file, watch directory. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, e.g., delete_index, get_index_stats, search_documents.

    Tool Count5/5

    7 tools cover the core operations for a file indexing server without being excessive or insufficient.

    Completeness5/5

    The tool set includes full lifecycle management: initial indexing, incremental updates, watching, listing, searching, stats, and bulk deletion. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues