com.docfork/docfork-mcp

\ Search a library's indexed documentation and return relevant sections with titles, summaries, and URLs. Results are sourced from official, versioned documentation. Usage: - Be specific in your query. Include the feature, API, or concept you need. Good: "server-side rendering with App Router". Bad: "rendering". - The library parameter accepts a simple name (e.g., react, nextjs) or exact owner/repo for precision (e.g., vercel/next.js, TanStack/query). - When multiple library candidates appear, prefer exact name matches and official organizations over forks. - After 2 searches without finding the relevant section, switch to fetch_doc on the best result URL or the library's documentation root rather than searching again. - Use fetch_doc on result URLs to retrieve full documentation content.

\ Retrieve full documentation content from a URL and return it as rendered markdown. Use this tool to get complete pages — including code examples, API signatures, and prose — from search_docs result URLs. - Pass a URL directly from search_docs results to retrieve that section's full content. - Trim the URL anchor or path to a parent directory to get a broader table of contents with section previews. - Returns rendered markdown that preserves code blocks, headings, and document structure. - Only works on Docfork-indexed documentation — use WebFetch for URLs not returned by search_docs. - If search_docs returns sparse or no results, try fetch_doc on the library's root documentation URL (e.g. https://github.com/owner/repo/tree/main/docs) to browse available content.