cowork-semantic-search
Related Servers
Alternatives to cowork-semantic-search
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenancePrivacy-first local document search using semantic search. Runs entirely on your machine with no cloud services, supporting PDF, DOCX, TXT, and Markdown files.92,426 npm417MIT
- FlicenseNot gradedqualityDmaintenanceEnables semantic search over personal files using natural language, with optional AI summarization, all running locally.-
- FlicenseAqualityDmaintenanceEnables indexing local documents (PDF, Markdown, text, code) into a knowledge base and querying them via semantic search using local embeddings, all running privately on your machine.4-
- AlicenseNot gradedqualityDmaintenanceProvides local semantic search over files using embeddings, enabling directory indexing and natural language queries without external services.41 PyPIMIT
- AlicenseAqualityBmaintenanceEnables developers to index and search their own local PDF, DOCX, Markdown, and text documents from an MCP client or terminal, combining semantic similarity with keyword matching for exact technical terms. Everything runs on the user's machine with no API key, Docker, or external database, so private documents stay private and work offline after the initial model download.92,426 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables private, offline semantic search across local files (documents, images, videos) using OCR and vector search, and optionally performs web research with cited sources.AGPL 3.0
TDQS
Scored across 4 tools
Tools cover distinct lifecycle stages: status check, folder indexing, querying, and forced single-file reindexing. The only mild overlap is between index_folder and reindex_file, but descriptions clarify bulk vs. targeted cache-bypassing use.
Three of four names follow verb_noun snake_case (get_index_status, index_folder, reindex_file). semantic_search is an adjective_noun outlier, but the overall pattern remains readable and consistent.
Four tools is a tight, well-scoped set for a focused semantic-search server. Each operation (index, query, status, targeted reindex) maps to a distinct user need without bloat.
Core index/search/reindex/status flows are covered, but there is no delete or remove-from-index operation. Deleted or moved files would leave stale chunks, creating a notable lifecycle gap.