M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
H

Hermes Atlas MCP Server

Community
Bring the Hermes Atlas ecosystem catalog to any MCP client.
How to install ↓ Compare GitHub source repository ↗
Category
Other #193 of 230
Stars
★ 134 Popular
Transport
stdio (local process)
Runtime
Node.js · Docker
Credentials
No credential needed
License
MIT
Last commit
Tools
6
43FMRS · D

This server provides a clean and practical way to access the Hermes Agent ecosystem catalog, with intuitive tools and installation. The live data nature is a strength, but the experimental status and third-party API dependency are potential considerations.

Strongest · Setup experience 12/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
10/20
Maintenance
8/20
Documentation
7/20
Setup experience
12/20
Why each score
Reliability 6/20
The manifest and README describe an npm stdio MCP server with tools and resources, so the happy path is plausible. However, no executable source, tests, or CI evidence is present in the reviewed material; the README says five tools while listing six, and repository/package naming is inconsistent. Error handling and diagnosable failure modes are not shown, so clean startup and handshake cannot be verified. Score: 6.
Security and permissions 10/20
No hardcoded secrets, malicious commands, or destructive defaults appear in the supplied material. However, ask_atlas sends user questions to a third-party /api/chat endpoint without a clear privacy/data-boundary disclosure, and the installer edits client config files with only a --force flag as an override. Least-privilege and confirmation behavior are incomplete. Score: 10.
Maintenance 8/20
MIT license, non-archived repository, version 0.2.0, and zero open issues indicate some maintenance. Yet there is no commit history, release evidence, dependency update trail, or security-response channel in the provided material; the README's weekly-release claim is untrusted, and maintainer identity appears inconsistent. Score: 8.
Documentation 7/20
Install instructions and per-client config examples are useful, and the tools/resources overview helps. Still, tool parameters, concrete call examples, limits/cost, and troubleshooting are missing, and the README contradicts itself with five tools vs. the six it lists. The documentation is usable but incomplete. Score: 7.
Setup experience 12/20
The one-command installer and client-specific JSON snippets give a clear few-step setup, with platform paths included. However, Node/npx runtime requirements are implicit, the clone path differs from the resulting working directory, and no CI or committed tests verify execution. Static calibration caps setup at 15; uncertainty lowers it to 12.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Developers and teams using Hermes Agent who want to discover community tools and integrations.
  • Users who want to access live catalog information through MCP clients like Claude Desktop, Cursor, etc.
  • Users who need up-to-date ecosystem data, as data is fetched live and cached briefly.

Not for

  • Users needing offline catalog access independent of the internet (data is fetched live from hermesatlas.com).
  • Users who want long-term caching or to avoid external API dependencies (optional Redis provides longer caching, but default is in-memory only).
  • Users needing official oversight or support, as this server is maintained by a contributor, not the official Hermes project.

Required permissions

  • Network access: fetch live catalog data and API requests from hermesatlas.com.
  • File system access: for the installer, read and write client config files (e.g., claude_desktop_config.json).
  • Optional: access to Redis if REDIS_URL is set.

Risks and side effects

  • Data is sourced from a third-party API (hermesatlas.com), which could affect reliability if the site or API changes.
  • The installer modifies client config files, which could break existing MCP setups if done incorrectly; use --print for a dry run.
  • Since the server is experimental (0.x), breaking changes may occur.

Setup

Before you start

Runtime：Node.js · Docker

Other optional settings (1)
REDIS_URL optional Optional Redis connection URL enabling a shared L2 cache across restarts and rate-limiting of ask_atlas; set it in .env after starting via docker compose up -d.

Recommended one-command install: npx -y hermes-atlas-mcp install --client claude-desktop (replace claude-desktop with cursor or claude-code). The installer finds the right config file for your OS and merges the hermes-atlas entry. Alternatively, manually edit the config file: for Claude Desktop, config is at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows), or ~/.config/Claude/claude_desktop_config.json (Linux); for Cursor, at ~/.cursor/mcp.json or .cursor/mcp.json. After adding the config, fully quit and reopen the client. For Claude Code, use the installer or run /mcp.

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

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "hermes-atlas": {
      "command": "npx",
      "args": [
        "-y",
        "hermes-atlas-mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add hermes-atlas -- npx -y hermes-atlas-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After fully restarting the client, the tools (search_projects, get_project, list_by_category, get_guide, ask_atlas, health_check) should appear in the tool picker; you can also call health_check to confirm server status and optional Redis connectivity.

Troubleshooting

  1. Ensure Node.js and npx are installed.
  2. If tools don't appear in the client, fully quit and reopen the client (closing the window isn't enough).
  3. Use the health_check tool to verify server status and Redis connectivity (if configured).
  4. Check the client config file for correct command and arguments, ensuring the mcpServers object is merged properly.
  5. If facing network issues, check firewall or proxy settings.

Things to try

Once connected, you can 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

Tools 6

health_check read-only
Check server status and optional Redis connectivity.
search_projects read-only
Ranked keyword search over the catalog, with optional category filter.
get_project read-only
Fetch full summary, metadata, and URL for a single 'owner/repo'.
list_by_category read-only
Get ranked projects from one of the six curated lists.
get_guide read-only
Fetch the full text of the beginner's guide, install guide, or vs-Claude Code comparison.
ask_atlas read-only
Route a free-form RAG question to the site's /api/chat endpoint.

Use cases

Search Hermes Atlas for tools, skills, or plugins.
Get summaries and metadata for projects in the Hermes Agent ecosystem.
List top skills or projects in a specific category.
Get the Hermes beginner's guide or compare Hermes Agent and Claude Code.
Ask the Atlas natural language questions about the ecosystem.

Supported clients

Claude Desktop
Cursor
Continue
Windsurf

Listed from the project's documentation, not tested by this site.

Overview

The Hermes Atlas MCP server provides live catalog data from hermesatlas.com, offering 100+ community-built tools, skills, plugins, memory providers, workspaces, and integrations for Nous Research's Hermes Agent. It includes search, project details, category listings, guides, and RAG-based Q&A functionality. Caching is in-memory (1-hour TTL) with optional Redis persistence (when REDIS_URL is set). The server is maintained by Kevin Simback and released under the MIT license.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 654 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision 1e587c70e7a4 Data synced 2026-08-12 Read the FMRS scoring method