Full Text Search Across Documents

via “text search and full-text indexing”

MongoDB Model Context Protocol Server

Unique: Integrates MongoDB's native text search indexes with MCP tools, enabling LLM clients to perform full-text queries without understanding MongoDB's $text operator syntax

vs others: Provides database-native text search (faster than application-level filtering) compared to vector-based semantic search, but lacks semantic understanding — best for keyword-based retrieval

via “typo-tolerant full-text search with inverted indexes”

Lightning-fast search engine with vector search.

Unique: Uses word_pair_proximity_docids indexes to track word adjacency during indexing, enabling proximity-aware ranking without post-search filtering. Charabia tokenization handles typo tolerance at index time rather than query time, avoiding expensive edit-distance calculations on every search.

vs others: Faster than Elasticsearch for typo-tolerant search because proximity indexes are pre-computed at index time rather than calculated at query time; simpler to deploy than Solr because it's a single Rust binary with no JVM overhead.

via “cross-lingual semantic search with language-agnostic queries”

sentence-similarity model by undefined. 70,32,108 downloads.

Unique: Trained on parallel sentence pairs across 94 languages using contrastive learning, creating a unified embedding space where queries and documents in different languages naturally cluster by semantic meaning. Achieves zero-shot cross-lingual retrieval without language-specific fine-tuning or translation, leveraging the model's learned understanding of semantic equivalence across language boundaries.

vs others: Eliminates need for query translation or language-specific model ensembles; more efficient than machine translation + monolingual search pipelines due to single-pass encoding; outperforms BM25 and TF-IDF on semantic relevance while maintaining multilingual support.

via “text search and full-text indexing”

A Model Context Protocol server to connect to MongoDB databases and MongoDB Atlas Clusters.

Unique: Exposes MongoDB's native text search capabilities through MCP tools, allowing agents to perform full-text search without external search engines, with built-in language support and relevance scoring

vs others: Simpler than integrating external search engines like Elasticsearch because it uses MongoDB's native text search, reducing infrastructure complexity for agents needing basic search functionality

via “multi-field full-text search with configurable tokenization”

Local-first document and vector database for React, React Native, and Node.js

Unique: Provides configurable tokenization and field-specific boosting in a local full-text search engine, whereas browser-native search APIs (Ctrl+F) lack relevance ranking and field weighting

vs others: Eliminates Elasticsearch dependency for basic full-text search with simpler API, though with lower performance on very large corpora (>1M documents)

via “unified document search with attribution-aware retrieval”

Centralize and orchestrate all your connections in one hub. Search across documents with unified, attribution‑aware retrieval and keep long‑lived workspace memory. Discover and run capabilities from every source with a single catalog, notifications, and multi‑workspace support.

Unique: Incorporates a unique metadata tagging system that ensures source attribution is preserved during document retrieval, unlike many standard search engines.

vs others: More reliable than traditional search engines as it maintains source citations, which is critical for academic and professional research.

via “contextual documentation search”

Discover and browse docs across libraries and frameworks. Search topics, skim high-level indexes, and open the exact pages you need. Fetch complete documentation when you require full-context analysis.

Unique: Utilizes a custom indexing engine that combines keyword matching with context-aware embeddings for better search accuracy.

vs others: More accurate than traditional keyword-based search engines due to its hybrid approach.

via “full-text sec document search”

Corporate credit data API for AI agents. Search bonds, leverage ratios, guarantors, corporate structure, and SEC filings across hundreds of companies. Screen high-yield bonds by YTM and seniority, resolve CUSIPs from free text, traverse guarantor hierarchies, and search full-text SEC documents.

Unique: Utilizes a custom-built indexing engine optimized for SEC document structures, enabling high-speed retrieval of relevant content.

vs others: More efficient than traditional document search tools due to its specialized indexing for SEC filings.

via “text search and full-text indexing”

** - Full Featured MCP Server for MongoDB Database.

Unique: Integrates MongoDB text search as an MCP capability, enabling Claude to perform full-text searches without constructing complex regex patterns, with language-aware stemming and stop word handling

vs others: More efficient than regex-based search because text indexes are optimized for keyword matching, providing sub-millisecond search latency on large text collections

via “full-text search (fts) query execution”

** - Interact with the data stored in Couchbase clusters using natural language.

Unique: Wraps Couchbase FTS as an MCP tool with automatic query translation and result ranking, enabling LLM agents to retrieve semantically relevant documents without understanding FTS query syntax. Integrates with RAG workflows for context injection.

vs others: More integrated than standalone search tools because it understands Couchbase's FTS indexing model and can combine FTS results with N1QL queries for hybrid search-and-query workflows within a single MCP interface.

via “full-text-search-with-advanced-filtering”

MCP server: scholarmcp

Unique: Exposes full-text search with advanced filtering as MCP tools, allowing agents to perform complex queries across paper abstracts and full text with structured filters, using inverted indexes for fast retrieval

vs others: Enables precise paper discovery compared to simple keyword search, allowing agents to combine multiple filter criteria and search full text rather than just titles and abstracts

via “semantic-search-across-document-collections”

An open source implementation of NotebookLM with more flexibility and features. [#opensource](https://github.com/lfnovo/open-notebook)

Unique: Open-source implementation allows choice of embedding models (local, open-source, or proprietary) and vector stores, whereas NotebookLM uses Google's proprietary embeddings. Supports hybrid search combining semantic and keyword matching for improved recall.

vs others: Provides transparency into embedding and retrieval mechanisms, enabling optimization for specific domains, versus NotebookLM's black-box search that cannot be customized or audited.

via “multi-document-semantic-search”

Tool for private interaction with your documents

Unique: Implements semantic search entirely locally using open-source embedding models and vector databases, avoiding dependency on proprietary search APIs (Elasticsearch, Algolia) while maintaining full control over ranking algorithms and metadata filtering

vs others: More semantically aware than keyword-based search (grep, Ctrl+F) and avoids cloud API costs compared to Azure Cognitive Search or AWS Kendra; slower than optimized cloud search for massive corpora but better privacy

via “semantic document search”

MCP server: search-docs

Unique: Utilizes a custom-built embedding model optimized for document context, allowing for more accurate semantic matches compared to traditional keyword searches.

vs others: More effective than traditional search engines like Elasticsearch for context-based queries, as it understands semantic relationships.

via “full-text search with keyword indexing and filtering”

AI-powered backend platform with Vector DB, DocumentDB, Auth, and more to speed up app development.

via “full-text and advanced document search”

via “full-text-search”

via “document search and retrieval at scale”

via “semantic-search-across-documents”

via “natural language document search”