cs2wt-docs-mcp
Related Servers
Alternatives to cs2wt-docs-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceLocal documentation search server for AI models using hybrid retrieval (phrase, keyword, vector). Provides MCP tools to search and fetch documentation from bundled or custom doc sets without any external API keys.-
- FlicenseAqualityCmaintenanceEnables AI agents to search, install, read, and navigate DevDocs documentation offline via MCP, with token-efficient search/read/toc tools and local caching.611 npm-
- FlicenseAqualityDmaintenanceScrapes, stores, and searches documentation locally, enabling AI assistants to access and query documentation via MCP.114-
- AlicenseAqualityBmaintenanceAn MCP server that provides AI assistants with searchable access to the full s&box game engine documentation and API reference.727 npm11MIT
- AlicenseNot gradedqualityCmaintenanceProvides a local MCP server for searching and retrieving documentation from 22+ open-source projects, enabling AI coding assistants to access up-to-date docs without network dependency.11 npm2MIT
- FlicenseNot gradedqualityCmaintenanceProvides LLMs with access to Payday 2 Lua documentation and source code via 7 MCP tools, enabling precise mod development queries.1-
TDQS
Scored across 3 tools
Each tool serves a clear, distinct purpose: search_docs for keyword lookup, get_page for retrieving a known page/section, and list_pages for enumerating the index. No overlap or ambiguity between them.
All tools follow the same snake_case verb_noun pattern: search_docs, get_page, list_pages. The naming is perfectly consistent and predictable.
Three tools is an ideal scope for a documentation retrieval server: search, fetch by identifier, and list coverage. Each tool earns its place with no redundancy.
The tool surface fully covers the core workflow for documentation access: discover via search, list available pages, and read page content by title or section. No obvious gaps for the stated purpose.