hermes-atlas-mcp

MCP server exposing the Hermes Atlas ecosystem catalog — 100+ community-built tools, skills, plugins, memory providers, workspaces, and integrations for Nous Research's Hermes Agent — to any MCP-aware client (Claude Desktop, Cursor, Continue, Windsurf, etc.).

Ask your AI assistant things like:

  • "Search Hermes Atlas for memory providers"
  • "What does the hermes-atlas catalog say about the hermes-agent project?"
  • "List the top skills for Hermes Agent"
  • "Get the Hermes beginner's guide"
  • "Ask the atlas: what's the difference between Hermes Agent and Claude Code?"

All catalog data is fetched live from hermesatlas.com (cached in-memory for 1 hour, with optional Redis persistence when REDIS_URL is set), so tool answers reflect the current ecosystem, not a stale snapshot.

Status: 0.x, experimental. Breaking changes may happen before 1.0. Batch releases weekly.

Install

Recommended — one command

npx -y hermes-atlas-mcp install --client claude-desktop

Replace claude-desktop with cursor or claude-code as needed. The installer finds the right config file for your OS, merges in the hermes-atlas entry without touching your other MCP servers, and tells you what to do next.

Other flags:

  • --print — dry-run (shows the diff, writes nothing)
  • --force — overwrite an existing hermes-atlas entry without prompting

To remove:

npx -y hermes-atlas-mcp uninstall --client claude-desktop

Fully quit and reopen the client after either command (closing the window isn't enough — the process needs to restart).

Manual install (if the installer won't work)

Claude Desktop

Find the config file:

  • Easiest: open Claude Desktop, go to Settings → Developer → Edit Config. The file opens in your default editor.
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

Paste this (if the file is empty or doesn't exist) or merge the hermes-atlas entry into your existing mcpServers object:

{
  "mcpServers": {
    "hermes-atlas": {
      "command": "npx",
      "args": ["-y", "hermes-atlas-mcp"]
    }
  }
}

Save. Fully quit Claude Desktop and reopen. The five tools appear in the tool picker.

Cursor

File: ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project). Same JSON snippet as above.

Claude Code

Either use the installer above, or run /mcp inside Claude Code and add through its UI, or hand-edit ~/.claude.json.

From source

git clone https://github.com/MoisesR7/hermes-mcp.git
cd hermes-atlas-mcp
npm install
npm run build
node dist/index.js    # stdio server, pipe JSON-RPC to test

Redis (optional)

Redis adds a shared L2 cache across MCP restarts and rate-limits ask_atlas:

docker compose up -d
cp .env.example .env
Data Cache TTL
Catalog JSON (repos, summaries, lists, etc.) 1 hour
get_guide 1 hour
ask_atlas 5 minutes

Without REDIS_URL, the server uses in-memory caching only. Use the health_check tool to verify Redis connectivity.

Tools

Tool What it does
health_check Server status and optional Redis connectivity.
search_projects Ranked keyword search over the catalog. Optional category filter.
get_project Full summary + metadata + URL for one owner/repo.
list_by_category Ranked projects in one of the six curated lists.
get_guide Full text of the beginner's guide, install guide, or vs-Claude-Code comparison.
ask_atlas Free-form RAG question routed to the site's /api/chat endpoint.

Resources

URI Content
hermes-atlas://repos Full catalog JSON
hermes-atlas://summaries AI-generated summaries JSON
hermes-atlas://lists Curated lists JSON
hermes-atlas://ecosystem ECOSYSTEM.md overview (markdown)

Development

npm install
npm run dev     # tsc --watch
npm run build   # tsc
npm start       # runs dist/index.js on stdio

License

MIT © Kevin Simback. Catalog data is CC0.

Related