hermes-docs-mcp
Provides searchable access to the installed Hermes Agent documentation, allowing agents to query, retrieve, and list documentation pages that match the installed version.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hermes-docs-mcpsearch the Hermes docs for how to configure MCP servers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hermes Docs MCP
MCP server that gives AI agents searchable access to the Hermes Agent documentation. It uses a local Hermes checkout when available, so documentation can match the installed version and be searched offline, with a GitHub fallback otherwise.
Tools
search_hermes_docs(query, limit): search indexed pages by title, slug, headings, environment variables, and content.get_hermes_doc(slug): retrieve a full page as compact Markdown. Accepts bare slugs and full documentation URLs.list_hermes_docs(section?, limit): list indexed pages, optionally filtered by section.
Related MCP server: mcp-doc-search
Installation
Requires Node.js 20 or later and npm. Clone this repository, open its directory, and run:
npm ci
npm test
npm run buildRun the server with npm start, or configure an MCP client to launch
node /absolute/path/to/hermes-docs-mcp/dist/cli.js over standard input and output.
The package is private in npm metadata; these instructions use a source checkout,
not an npm registry installation.
Documentation source
By default, the server checks ~/.hermes/hermes-agent/website/docs. When that
local checkout exists, its documentation reflects that checkout's version. Search
and list results include the local Git commit when available, or unknown otherwise.
The local index refreshes after a short cache interval when another request arrives.
Without the default local directory, the server fetches documentation from the
main branch of NousResearch/hermes-agent on GitHub. This requires network access
and may describe a different version than your installed Hermes Agent.
To explicitly select a local documentation directory:
HERMES_DOCS_DIR=/path/to/hermes-agent/website/docs npm startAn explicit directory must exist; it does not fall back to GitHub on error.
Hermes configuration example
Add the following entry to your Hermes configuration file, adjusting the absolute path to your checkout. Configuration is not installed automatically.
mcp_servers:
hermes-docs:
command: "node"
args: ["/absolute/path/to/hermes-docs-mcp/dist/cli.js"]
timeout: 180
connect_timeout: 60
enabled: trueIf your client cannot find node, use the absolute path to your Node.js executable.
This server cannot be deployed
Maintenance
Related MCP Connectors
Versioned documentation registry and semantic search for AI tools and coding assistants.
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
Team docs served to AI agents over MCP - search, Markdown reads, version pinning, read audit.
One place for every AI agent's pages and docs: versioned links to share, search and update.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceServes RootApp documentation files with search and retrieval capabilities, enabling users to access specific docs, browse directory structure, and search across file names and content.AGPL 3.0
- AlicenseBqualityDmaintenanceEnables searching and retrieving documentation files from a local docs folder using a search tool and dynamic resource URIs.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 gradedqualityCmaintenanceEnables MCP clients to search, navigate, and read the complete Hermes Agent documentation through a local SQLite FTS5 index, with tools for full-text search, page reading, and browsing documentation structure.MIT