"Scraping a marketplace to generate a JSON file with name, description, and link" matching MCP servers:

Enables users to ingest PDF/DOCX/TXT/MD documents and ask natural language questions about them, using local embeddings and Groq-powered retrieval-augmented generation.

Provides retrieval-augmented generation (RAG) capabilities by ingesting various document formats into a persistent ChromaDB vector store. It enables semantic search and retrieval using either OpenAI or Ollama embeddings for processing local files, directories, and URLs.

MCP server that ingests PDF documents into pgvector for semantic search and RAG pipelines. It handles extraction, chunking, local embeddings, and storage, enabling agents to make PDFs searchable via natural language.

MCP server that provides secure read-only access to a local folder, enabling file listing, reading, semantic search (RAG), and indexing status via natural language, integrated with Claude Desktop and a custom agent loop.

A lightweight RAG system that provides an MCP server for searching and interacting with vector-based knowledge bases. It enables users to perform retrieval-augmented generation and search across Qdrant collections through a standardized interface.

Facilitates knowledge graph representation with semantic search using Qdrant, supporting OpenAI embeddings for semantic similarity and robust HTTPS integration with file-based graph persistence.

This server enables semantic search capabilities using Qdrant vector database and OpenAI embeddings, allowing users to query collections, list available collections, and view collection information.

Enables hybrid search (BM25 + semantic with RRF) over documentation, with Thai language support. It exposes MCP tools for adding documents and searching via Qdrant and Ollama/OpenAI, using a stateless Streamable HTTP transport.

Enables storing and retrieving text in a local vector store using Qdrant, running fully locally with no external database or API key.

Enables natural language search and analysis of uploaded PDF, CSV, and Excel documents using retrieval-augmented generation and MCP tools, providing contextual answers to user queries.

MCP server for OpenAI Vector Store API, managing vector stores, files, file batches, and semantic search.

An MCP server that retrieves resume/experience evidence relevant to a job description via vector RAG, and tracks fit-analysis results in a configurable tracking store (Notion or SQLite), with tools like match_job, push_to_tracker, and list_applications.

A Model Context Protocol (MCP) server that provides a local-first RAG engine for your markdown documents. It uses a file-based Milvus vector database to index your notes, enabling LLMs to perform semantic search and retrieve relevant content from your local files.

ArcadeDB Multi-Model Database, one DBMS that supports SQL, Cypher, Gremlin, HTTP/JSON, MongoDB and Redis. ArcadeDB is a conceptual fork of OrientDB, the first Multi-Model DBMS. ArcadeDB supports Vector Embeddings.

Local-first memory for Claude Code and any MCP client: hybrid vector + keyword search and a bi-temporal knowledge graph in one SQLite file. Local embeddings, no API key, $0/token.

Enables users to build and manage a complete retrieval-augmented generation pipeline through conversation, including file ingestion, collection management, hybrid search, reranking, citations, and a guided setup wizard.

An MCP server that provides persistent semantic memory for LLMs by building a concept graph with vector search. It enables storing, linking, and retrieving concepts across conversations using Turso vector search and 256-dimensional embeddings.

Enables AI agents to manage and search data in Redis using natural language. Supports hashes, lists, sets, sorted sets, streams, JSON, and vector search.

A Model Context Protocol (MCP) server for advanced code analysis and editing with semantic search capabilities, enabling AI assistants to perform complex code operations through a standardized interface.

Enables Claude to store and query personal finance transactions using semantic search. Transactions are persisted in ChromaDB and JSON, allowing natural language questions about spending trends and portfolio allocations.