Hermes Atlas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_reposA | Search the Hermes Atlas ecosystem for repos matching a query. Searches across repo names, descriptions, categories, and owners. Returns ranked results with star counts and official badges. |
| list_categoriesA | List all ecosystem categories with repo counts. Useful for discovering what types of tools exist in the Hermes ecosystem. |
| get_repoA | Get detailed information about a specific repo including its AI-generated summary, highlights, and category. Use owner/repo format (e.g. 'NousResearch/hermes-agent'). |
| recommendA | Get personalized recommendations for Hermes ecosystem tools based on a use case description. Matches repos using AI-generated summaries and highlights. Great for answering 'what should I use for X?' questions. |
| get_featuredA | Get currently featured/trending repos in the Hermes ecosystem — the best new additions and rising projects. |
| get_listsA | Get curated lists (best memory providers, top skills, deployment options, etc.). Each list has a title, description, and per-repo descriptions. |
| get_listB | Get a specific curated list with per-repo descriptions and recommendations. |
| ecosystem_statsA | Get aggregate ecosystem statistics — total repos, total stars, category breakdown, latest Hermes version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct function: stats, featured repos, curated lists, single repo details, categories, personalized recommendations, and search. No two tools have overlapping purposes, minimizing agent confusion.
Most tools follow a verb_noun pattern with underscores (get_featured, get_list, search_repos), but ecosystem_stats uses noun_verb and recommend lacks an underscore, creating mild inconsistency.
Eight tools are appropriate for an ecosystem explorer, covering search, browsing, recommendations, and stats without being overwhelming or sparse.
The set covers key exploration tasks: searching, filtering by category or list, getting details, and recommendations. Missing is a bulk listing of all repos, but search_repos can substitute, so only minor gaps.