rokadoc MCP Server
Related Servers
Alternatives to rokadoc MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables any MCP-compatible application to perform advanced multi-modal document processing and retrieval using RAG-Anything.MIT
- FlicenseNot gradedqualityDmaintenanceA RAG service based on FastMCP that enables document indexing and retrieval (keyword/vector search) through the MCP protocol.-
- AlicenseNot gradedqualityDmaintenanceProvides semantic search over markdown documentation using RAG, allowing natural language queries and integration with MCP clients.1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Retrieval-Augmented Generation (RAG) operations. It provides tools for building and querying vector-based knowledge bases from document collections, enabling semantic search and document retrieval capabilities.3MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides document analysis capabilities to LLM applications, including extraction, chunking, summarization, and semantic search for PDF, DOCX, and plaintext documents.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server for document parsing, ingestion, query (including multimodal), and lightweight knowledge graph inspection, enabling RAG workflows via the Model Context Protocol.-
TDQS
Scored across 4 tools
Each tool targets a distinct action on a distinct resource: submitting a conversion, listing jobs, fetching a job result, and RAG-searching documents. There is no meaningful overlap between the submission and retrieval tools, and search_documents is clearly separate.
All four tools follow a consistent snake_case verb_noun pattern (list_conversions, get_conversion_result, search_documents, convert_document). No deviations in style or convention.
Four tools is a reasonable, focused surface for a document conversion + RAG service, though it leans slightly thin. Each tool earns its place without redundancy.
The core workflow (submit conversion, list jobs, fetch result, search) is covered, but there is no way to delete or cancel a conversion/document or fetch document metadata. These gaps limit lifecycle management.