pdfdancer-mcp
Related Servers
Alternatives to pdfdancer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.720 npm1MIT
- FlicenseNot gradedqualityCmaintenanceProvides read-only MCP tools for hybrid semantic and keyword search over locally indexed PDF documentation, with citations and context retrieval for LLM agents.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access and search MkDocs documentation through tools for full-text search, page navigation, and code block extraction. It serves documentation pages as readable resources and provides structural outlines to help LLMs navigate documentation content.MIT
- AlicenseNot gradedqualityDmaintenanceProvides direct access to local documentation files through simple search and overview tools, enabling LLMs to query project-specific markdown documentation without requiring vector databases or RAG pipelines.MIT
- FlicenseNot gradedqualityDmaintenanceIndexes PDF documents into Qdrant and exposes semantic search as MCP tools, enabling RAG-based interactions with your documents.-
- AlicenseAqualityDmaintenanceProvides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.39 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get-docs retrieves full documentation content, help explains the server's purpose, search-docs searches documentation by keyword, and version returns the server version. An agent can easily tell these tools apart as they target different functionalities.
The naming is mixed with some consistency issues: get-docs and search-docs follow a verb_noun pattern with hyphens, but help and version are single words without a clear pattern. This mixed convention reduces predictability, though the names remain readable.
With 4 tools, the count is reasonable for a documentation-focused server, covering core operations like searching, retrieving, and getting help. It is slightly under-scoped as it lacks tools for interacting with PDFDancer's actual functionality (e.g., processing PDFs), but the tools provided are well-justified for their stated purpose.
The tool surface is severely incomplete for a server named 'pdfdancer-mcp', which implies PDF manipulation capabilities. It only provides documentation access and meta-tools (help, version), with no tools for creating, editing, or processing PDFs. This creates significant gaps that will cause agent failures when trying to perform PDF-related tasks.