Hermes Atlas Mcp

io.github.ksimbackPublished by GitHub account ksimbackv0.2.0Updated Oct 25, 2026

Search and fetch 100+ Hermes Agent tools, skills, plugins, and integrations from hermesatlas.com.

The publisher's own server: Red Atlas Api

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant search and read the Hermes Atlas catalog of community tools, skills, plugins and integrations for Hermes Agent.

What you can do
Search the catalog by keyword, optionally filtered by category, and list ranked projects within curated categories. Fetch a full summary, metadata and link for a single project by owner/repo. Read the beginner's guide, install guide and a comparison with Claude Code. Ask free-form questions answered through the site's chat endpoint. Read the full catalog, summaries, curated lists and ecosystem overview as resources.
When to use it
Useful when you are exploring or choosing add-ons for Nous Research's Hermes Agent and want an assistant to look up projects, compare options or pull the beginner's guide without browsing the site manually.
Requirements
Runs locally over stdio, normally launched with npx from the npm package, so Node.js is needed. No accounts, API keys or environment variables are declared. It fetches catalog data live from hermesatlas.com, so network access is required.
Before you install
Catalog data and free-form questions are sent to hermesatlas.com, including whatever text you put into the ask-atlas tool. The project is marked 0.x experimental, so breaking changes are possible. The installer writes to your MCP client configuration file; a dry-run flag exists to preview changes.

Installation

In SourceWeft

  1. Open Hermes Atlas Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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), 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

bash
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:

bash
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:

json
{  "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

bash
git clone https://github.com/ksimback/hermes-atlas-mcp.gitcd hermes-atlas-mcpnpm installnpm run buildnode dist/index.js    # stdio server, pipe JSON-RPC to test

Tools

ToolWhat it does
search_projectsRanked keyword search over the catalog. Optional category filter.
get_projectFull summary + metadata + URL for one owner/repo.
list_by_categoryRanked projects in one of the six curated lists.
get_guideFull text of the beginner's guide, install guide, or vs-Claude-Code comparison.
ask_atlasFree-form RAG question routed to the site's /api/chat endpoint.

Resources

URIContent
hermes-atlas://reposFull catalog JSON
hermes-atlas://summariesAI-generated summaries JSON
hermes-atlas://listsCurated lists JSON
hermes-atlas://ecosystemECOSYSTEM.md overview (markdown)

Development

bash
npm installnpm run dev     # tsc --watchnpm run build   # tscnpm start       # runs dist/index.js on stdio

License

MIT © Kevin Simback. Catalog data is CC0.

Related

Source: README.md at commit bf02609

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Atlas integrations