|

Nous Research Ships Hermes Agent Profile Builder: Identity, Model, Skills, and MCP Servers in One Dashboard Flow

ByRicardo

Nous Research has shipped a Profile Builder for Hermes Agent. It lives contained in the challenge’s native internet dashboard. Standing up a definite agent used to imply a number of CLI steps. The builder now walks you thru one guided stream.

In that stream you outline an agent’s id. You choose a mannequin and supplier. You select built-in and non-obligatory abilities. You set up abilities from the hub. You connect MCP servers.

Hermes Agent is Nous Research’s open-source, self-improving agent. It runs on the CLI, a desktop app, and messaging platforms. Profiles had been beforehand assembled largely by terminal instructions. The Profile Builder brings these items right into a browser type.

Profile Builder

A profile in Hermes is a separate residence listing. Each profile holds its personal config.yaml, .env, and SOUL.md. It additionally retains separate reminiscence, classes, abilities, cron jobs, and a state database.

Profiles allow you to run remoted brokers on one machine. A coding agent and a analysis agent by no means share state. This is the unit the builder produces.

You launch the dashboard by operating hermes dashboard. It opens at http://127.0.0.1:9119 in your browser. The default bind is loopback, so no knowledge leaves localhost. The builder collects the identical inputs the CLI profile instructions settle for. It then writes them into the profile’s recordsdata.

The Fields the Builder Configures

The builder gathers 5 teams of settings in one place:

  • First is id, a reputation and an outline. The identify additionally turns into a shell command alias. Create a profile named coder and you get coder chat. Deeper character lives in the profile’s SOUL.md file.
  • Second is the mannequin and supplier. Hermes helps Nous Portal, OpenRouter, NVIDIA, OpenAI, and extra. You may level at your personal OpenAI-compatible endpoint.
  • Third is built-in abilities, toggled on or off per profile.
  • Fourth is Skills Hub installs, pulled from exterior catalogs by identifier.
  • Fifth is MCP servers, added by URL or by native command.

Two of those phrases deserve a brief rationalization.

Skills are SKILL.md recordsdata with a reputation, an outline, and a process. The agent reads quick descriptions cheaply. It hundreds a ability’s full content material solely when a activity wants it. So including many abilities doesn’t bloat each request.

MCP servers expose exterior instruments by the Model Context Protocol. Hermes accepts HTTP servers by way of a URL. It additionally accepts stdio servers by way of a neighborhood command. A Nous-approved catalog affords one-click installs, prompting inline for any keys.

GUI Flow vs the CLI Sequence

The builder doesn’t substitute the CLI. It mirrors it in a type. The desk beneath maps every step to its command equal.

Step Profile Builder (dashboard) CLI equal
Create and identify Name area hermes profile create coder
Description Description area --description "..." or hermes profile describe
Model and supplier Model picker coder config set mannequin <id>
Built-in abilities Toggles coder abilities record / toggle
Skills Hub set up Search and set up coder abilities set up <slug>
MCP servers Add or catalog set up edit mcp_servers / coder mcp set up

Both paths edit the identical profile listing. The builder is the lower-friction entry level. The CLI stays the scriptable one.

Use Cases With Examples

  • The first use case is a targeted coding assistant. Give it a code-aware mannequin and a filesystem MCP server. Add Git and testing abilities. Keep its reminiscence scoped to at least one challenge.
  • The second is a analysis agent. Pair a succesful mannequin with web-extract abilities. Its findings keep separate out of your different brokers. Cloning the profile later preserves that separation.
  • The third is an operations bot. Attach a messaging channel and schedule cron experiences. Each profile runs its personal gateway and bot token. Token locks block two profiles from sharing a token accidentally.

In every case, the builder produces one remoted agent. You can run a number of with out state collisions.

What the Builder Writes

The builder edits recordsdata the CLI already reads. Model and supplier land in the profile’s config.yaml. MCP servers populate the mcp_servers block in that file. API keys go to the profile’s .env.

The equal CLI sequence for a analysis profile seems like this:

Copy Code
hermes profile create researcher 
  --description "Reads supply code and exterior docs, writes findings."
researcher setup                      # configure API keys + mannequin
researcher config set mannequin anthropic/claude-sonnet-4
researcher abilities set up openai/abilities/k8s

An identical config.yaml for that profile. Note that mcp_servers is a map keyed by server identify, not a listing:

Copy Code
# ~/.hermes/profiles/researcher/config.yaml
mannequin:
  default: anthropic/claude-sonnet-4

mcp_servers:
  filesystem:
    command: npx
    args: ["-y", "@modelcontextprotocol/server-filesystem", "/home/user/projects"]

A distant HTTP MCP server makes use of url and headers as a substitute of command:

Copy Code
mcp_servers:
  docs:
    url: "https://mcp.instance.com/mcp"
    headers:
      Authorization: "Bearer ${DOCS_API_KEY}"

Reaching the builder requires the dashboard further. The base set up ships with out the HTTP stack.

Install it with one command:

Copy Code
pip set up 'hermes-agent[web]'

Strengths and Limitations

Strengths:

  • One stream replaces a number of CLI steps for a brand new profile.
  • Identity, mannequin, abilities, and MCP sit in one place.
  • Output stays in normal config.yaml and .env recordsdata.
  • The dashboard runs regionally and binds to loopback by default.
  • The catalog handles MCP and Skills Hub installs inline.

Limitations:

  • Profiles don’t sandbox filesystem entry on the native backend.
  • A non-loopback bind fails closed until an auth supplier is configured.
  • Skill and MCP adjustments take impact on the following session or gateway restart.
  • The builder surfaces controls that additionally reside on separate dashboard pages.

Marktechpost’s Interactive Explainer

Nous Research · Hermes Agent
The Profile Builder, defined

DEMOsimulation, not the reside product


Becomes a command → researcher chat


Each profile is its personal remoted residence listing.



Switch any time with hermes mannequin.

Off → written to agent.disabled_toolsets.



mcp_servers is a map keyed by server identify.

~/.hermes/profiles/researcher/config.yaml







  Marktechpublish

  AI analysis and tooling, decoded for builders. Independent demo by Marktechpost — not affiliated with Nous Research.

  marktechpost.com →















Check out the next Hermes sources: Web Dashboard — Hermes Agent docs, Configuration — Hermes Agent docs, Profiles: Running Multiple Agents — Hermes Agent docs, MCP Config Reference — Hermes Agent docs, and Quickstart — Hermes Agent docs. 


Also, be at liberty to observe us on Twitter and don’t neglect to affix our 150k+ ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.


Need to companion with us for selling your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar and many others.? Connect with us


The publish Nous Research Ships Hermes Agent Profile Builder: Identity, Model, Skills, and MCP Servers in One Dashboard Flow appeared first on MarkTechPost.








	

	





	

		

			

				

					
Similar Posts