VibeCTX
Related Servers
Alternatives to VibeCTX
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI coding agents to search, index, and manage documentation libraries with hybrid retrieval and live web fallback, all self-hosted and offline.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides up-to-date documentation for AI agents by locally querying a community-driven registry of pre-built docs packages.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search locally indexed documentation entirely offline, resolving libraries and retrieving relevant Markdown fragments under a token budget through SQLite FTS5 full-text search. Docs never leave the machine, with no API keys or cloud dependencies.1MIT
- AlicenseAqualityBmaintenanceA local MCP server that fetches official library documentation (llms.txt-first), caches it to disk, and serves relevant sections to coding agents offline with deterministic retrieval.310 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to fetch current, version-accurate library documentation at request time instead of relying on training memory, with search for answering questions and full-fidelity retrieval of pages or specific declarations. Supports bare or module-path library names, version pinning, and disambiguation when names collide.47 npmMIT
- FlicenseAqualityDmaintenanceScrapes documentation sites, chunks and embeds content locally, then retrieves relevant passages for queries. Enables agents to ask questions grounded in documentation.1-
TDQS
Scored across 8 tools
Most tools have clearly distinct roles (search vs get_docs are explicitly differentiated by 'unknown library' vs 'known library', and resolve_library vs warm_project by single-name vs whole-project). Minor overlap exists between doctor and list_libraries, both of which report per-library cache/retrieval status, which could cause slight misselection.
All names use consistent snake_case with a verb-oriented style (list_libraries, get_docs, resolve_library, warm_project, report_bug). A few are bare verbs (search, refresh, doctor), which is a minor deviation but still readable and predictable.
Eight tools is well-scoped for a documentation retrieval server, covering listing, fetching, searching, refreshing, diagnosing, resolving, bulk-warming, and reporting. Each tool has a distinct purpose and earns its place.
The lifecycle is largely covered: discovery, retrieval, search, caching/warming, diagnostics, resolution, and bug reporting. Minor gaps exist, such as no explicit cache-clear/prune operation or arbitrary-URL fetch, but core workflows are fully supported.