LlamaIndex Docs MCP lets AI agents search and navigate LlamaIndex documentation using semantic search, exact text and regex matching, documentation browsing, and direct page reading for accurate technical guidance.
Hermes is Nous Research's command-line agent. MCP servers are declared in its YAML config and reloaded without a restart.
This guide connects LlamaIndex Docs MCP to Hermes through MewCP, so Hermes can use LlamaIndex Docs MCP's 4 tools, like search_docs, grep_docs and read_doc.
LlamaIndex Docs MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
Manage repositories, pull requests, issues, branches and development workflows on GitHub. Automate software delivery and collaborate across engineering projects.
Connect to external APIs, webhooks and internet services through standard HTTP requests. Build integrations with virtually any platform that exposes a web-based interface.
Give AI coding agents access to a curated library of real-world website designs, screenshots, design systems, and reusable UI components. Search visual references, find similar designs, analyze layouts, extract colors and typography, compare websites, and retrieve copy-ready JSX components for building better interfaces
HotAPI provides a unified API for AI-powered image, video, and audio generation, image editing, and conversational AI. Developers can access multiple models through a single API key, track asynchronous generation tasks, and retrieve results with polling or webhooks.
Other clients
LlamaIndex Docs MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact LlamaIndex Docs MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Edit config.yaml in your Hermes config directory (~/.hermes).
Put this under the top-level "mcp_servers:" key.
Run /reload-mcp in Hermes, or start a fresh session. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Search through llama-index documentation using BM25 ranked search. Best for conceptual queries, finding documentation by topic, or when you're not sure of exact terminology. Returns ranked results with excerpts showing match context. Use this when: exploring unfamiliar topics, looking for 'how to' guides, searching by concept rather than exact terms, or need to understand what documentation exists on a subject. For exact term matching or code patterns, use grep_docs instead.
Search for exact text or regex patterns across documentation files. Returns all matching lines with their file locations and optional surrounding context. Best for: finding specific class/function names, locating exact error messages or code snippets, discovering all occurrences of a term, or pattern matching with regex. Unlike search_docs which ranks by relevance, this returns ALL matches in order. Use when you know precise terminology or need exhaustive results. Can return up to 500 matches vs search_docs' 20 result limit.
Read content from a specific documentation file by its path. By default returns the first 500 lines to avoid overwhelming context. Use startLine/endLine to read specific portions of longer documents. Accepts URL-style paths (e.g., '/python/framework/query-engine') or paths without extensions. Best for: reading documentation pages, understanding context after finding relevant excerpts, or accessing files you already know the path to.
Browse the documentation site structure to discover what pages and sections exist. Returns a tree showing directory slugs (usable as read_doc paths) and labels. Default depth is 1 (compact overview) when no section is specified, or 2 when a section/path is specified. Use depth=2-3 to see more detail. The path parameter performs a strict lookup — on a miss no tree is returned, just a short not-found message listing the searched sections; call again without path to browse.
