F
licenseC
qualityD
maintenanceProvides AI tools with access to HytaleModding.dev documentation through search and page retrieval, enabling modding assistance in natural language.
2
2
-
ProudNet Document MCP
Officialby Nettention
Related Servers
Alternatives to ProudNet Document MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides AI agents with access to the Colyseus documentation, enabling searching, reading, and listing of documentation pages.314 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables searching and fetching documentation pages from a wide range of programming languages, frameworks, game engines, and tools. Supports multiple sources and returns relevant documentation snippets.1-
- AlicenseBqualityDmaintenanceEnables developers to search and access NicePay payment API documentation, including endpoint details, code samples, and SDK method information through natural language queries.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Doxygen-generated XML documentation, including searching symbols, retrieving documentation, and listing class members for a specified library.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides tools to search and retrieve detailed documentation for the Kiwoom REST API, including parameters, categories, and code examples. It enables LLMs to generate request snippets in multiple programming languages to facilitate financial trading API integration.-
TDQS
B3.4/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: get_proudnet_page retrieves content from a specific page, list_proudnet_sections lists main sections, and search_proudnet_docs searches for topics. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_proudnet_page, list_proudnet_sections, search_proudnet_docs). The naming is predictable and readable throughout the set, with no deviations in style.
Tool Count4/5
With 3 tools, the count is reasonable for a documentation server, covering key operations like retrieving, listing, and searching. It is slightly minimal but well-scoped, as each tool serves a distinct and necessary function without feeling thin.
Completeness4/5
The tool surface covers essential documentation interactions: getting specific content, listing sections, and searching. Minor gaps might include operations like updating or managing documentation, but for a read-only documentation domain, the coverage is sufficient for agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues