mcp-plesk-dev-docs
Related Servers
Alternatives to mcp-plesk-dev-docs
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceProvides semantic search capabilities over the Plesk Extensions Guide documentation using Retrieval-Augmented Generation (RAG) and vector embeddings. It enables AI assistants to retrieve relevant technical information and answer natural language queries regarding Plesk extension development.-
- AlicenseNot gradedqualityFmaintenanceProvides a RAG-based search system for 1C:Enterprise platform documentation using hybrid BM25 and semantic search across multiple versions. It enables developers to retrieve API signatures, methods, and usage examples directly within IDEs or through a REST API.22MIT
- FlicenseNot gradedqualityDmaintenanceEnables semantic search over Jimdo help documentation to find relevant information and answers.-
- AlicenseAqualityBmaintenanceAccess to 819+ documentation sources from devdocs.io with semantic search capabilities.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search documentation of packages and services to find implementation details, examples, and specifications.MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search and retrieve information from large technical documentation (OpenAPI specs, markdown) via intelligent chunking and semantic search.MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose. Search, file retrieval, reference resolution, indexing operations, system health, and profile management are all separate concerns with no overlapping functionality.
Most tools follow a verb_noun pattern (e.g., get_file_content, trigger_index_sync), but 'search_mcp_plesk_dev_docs' includes the server name, and 'daemon_health' is noun_noun. These minor deviations from the dominant pattern prevent a perfect score.
With 10 tools, the set is well-scoped for a documentation server that includes indexing, search, and system health. Each tool serves a clear function without unnecessary bloat or sparseness.
The tool set covers the core lifecycle: indexing (refresh, trigger, check), search, retrieval, reference resolution, and system management. Minor gaps exist, such as the lack of a tool to list documentation sections or metadata, but these are not critical.