openmemory-rag-mcp
Related Servers
Alternatives to openmemory-rag-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for document ingestion and semantic search on Qdrant. Enables ingesting local documents, generating embeddings with OpenAI, and performing vector search with metadata filters.Apache 2.0
- AlicenseBqualityDmaintenanceA complete MCP server for Retrieval-Augmented Generation with file management and vector memory for agents. Supports multiple document formats (PDF, DOCX, TXT, MD, CSV, JSON) with semantic search using Hugging Face embeddings and ChromaDB for efficient vector storage.119 npm1MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for semantic search over PDF documents using RAG, pgvector, and OpenAI embeddings. Includes a web app for document upload and management.-
- FlicenseNot gradedqualityBmaintenanceA fully local MCP server that imports Markdown, PDF, and web pages into a running knowledge base, providing hybrid search and document retrieval via authenticated Streamable HTTP for Codex and DeepSeek agents.-
- FlicenseNot gradedqualityCmaintenanceMCP 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.-
- AlicenseNot gradedqualityBmaintenanceMCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.7 npmMIT
TDQS
Scored across 4 tools
The three import tools are clearly distinguished by source type (file, URL, raw text), and search_knowledge is obviously the retrieval counterpart. There is no meaningful overlap or ambiguity among these tools.
All tools follow a consistent verb_noun pattern: import_file, import_url, import_text, search_knowledge. The naming convention is uniform and predictable.
Four tools is well-scoped for an RAG knowledge base focused on ingestion and retrieval. Each tool covers a distinct and necessary operation without redundancy or bloat.
The core workflow of adding knowledge via three input types and searching it is covered. Minor gaps exist, such as no list, delete, or clear knowledge base operations, but they are not essential to the primary import-and-search purpose.