Citepath
Related Servers
Alternatives to Citepath
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceIndex any documentation website and search it from AI coding assistants via the Model Context Protocol (MCP).17 npm11MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Code and Cursor to search a documentation corpus, read specific pages, and locally ask grounded questions with verified citations over stdio or Streamable HTTP.MIT
- FlicenseNot gradedqualityDmaintenanceIndexes documentation sites by base URL and serves keyword search, optional semantic search, and Markdown page retrieval as MCP tools, all from a single SQLite file.-

Cactus MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceConnects MCP clients such as Claude, ChatGPT, Cursor and VS Code to a product's published help pages, product map, release timeline and past support conversations, letting users search, read, ask questions with cited answers, and run code-backed investigations. It also offers a sign-in-free server per public help center for visitor-style help search and team contact.MIT- FlicenseNot gradedqualityBmaintenanceA local MCP server that lets AI hosts like Claude Desktop, Cursor, or Cline query a hybrid vector + BM25 index of your scattered notes, project docs, PDFs, and chat exports, returning answers with section-level citations. It exposes eight tools, resources, and prompts so agents can search, ask, and walk links across all your source directories at once.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to query a local, hybrid-searchable second brain over scattered notes, documents, and chat logs with section-level citations. It exposes retrieval tools, resources, and prompts through MCP so hosts like Claude Desktop, Cursor, and Cline can use the indexed knowledge.-
TDQS
Scored across 3 tools
Each tool targets a distinct action: search finds passages, get_passage retrieves a specific passage by ID, and list_sources enumerates available sources. The descriptions explicitly clarify the intended workflow (e.g., 'Start here' for search, 'after search has found it' for get_passage), leaving no overlap.
Two tools follow a clear verb_noun pattern (get_passage, list_sources) in snake_case, but 'search' is a bare verb without a noun. This minor deviation is readable and common, but not fully consistent with the established pattern.
The server's narrow purpose (documentation search and passage retrieval) is served by exactly three well-scoped tools: finding content, drilling into specific passages, and listing sources. Each tool is necessary, and the count sits at the low end of the recommended 3-15 range without feeling thin.
The read-only surface covers the essential workflow: discover sources, search across them, and retrieve full passages with neighborhood context. Source management is intentionally delegated to the CLI, so no obvious gaps exist for the MCP role.