Nous Research Ships Hermes Agent Profile Builder: Identity, Model, Skills, and MCP Servers in One Dashboard Flow Nous Research released a Profile Builder for its open-source Hermes Agent, consolidating agent identity, model selection, skills, and MCP server configuration into a single guided flow within a local web dashboard. The tool replaces multiple CLI steps by allowing users to define an agent's name, description, model provider, built-in and hub-installed skills, and external tool connections through a browser form at `http://127.0.0.1:9119`. This enables running multiple isolated agents—such as a coding assistant, research bot, or operations tool—on one machine without shared state, with all data remaining on localhost. Nous Research has shipped a Profile Builder for Hermes Agent. It lives inside the project’s local web dashboard. Standing up a distinct agent used to mean several CLI steps. The builder now walks you through one guided flow. In that flow you define an agent’s identity. You pick a model and provider. You choose built-in and optional skills. You install skills from the hub. You attach 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 were previously assembled mostly through terminal commands. The Profile Builder brings those pieces into a browser form. Profile Builder A profile in Hermes is a separate home directory. Each profile holds its own config.yaml , .env , and SOUL.md . It also keeps separate memory, sessions, skills, cron jobs, and a state database. Profiles let you run isolated agents on one machine. A coding agent and a research agent never share state. This is the unit the builder produces. You launch the dashboard by running hermes dashboard . It opens at http://127.0.0.1:9119 in your browser. The default bind is loopback, so no data leaves localhost. The builder collects the same inputs the CLI profile commands accept. It then writes them into the profile’s files. The Fields the Builder Configures The builder gathers five groups of settings in one place: First is identity, a name and a description. The name also becomes a shell command alias. Create a profile named coder and you get coder chat . Deeper personality lives in the profile’s SOUL.md file. Second is the model and provider . Hermes supports Nous Portal, OpenRouter, NVIDIA, OpenAI, and more. You can also point at your own OpenAI-compatible endpoint. Third is built-in skills, toggled on or off per profile. Fourth is Skills Hub installs, pulled from external catalogs by identifier. Fifth is MCP servers, added by URL or by local command. Two of these terms deserve a short explanation. Skills are SKILL.md files with a name, a description, and a procedure. The agent reads short descriptions cheaply. It loads a skill’s full content only when a task needs it. So adding many skills does not bloat every request. MCP servers expose external tools through the Model Context Protocol. Hermes accepts HTTP servers via a URL. It also accepts stdio servers via a local command. A Nous-approved catalog offers one-click installs, prompting inline for any keys. GUI Flow vs the CLI Sequence The builder does not replace the CLI. It mirrors it in a form. The table below maps each step to its command equivalent. | Step | Profile Builder dashboard | CLI equivalent | |---|---|---| | Create and name | Name field | hermes profile create coder | | Description | Description field | --description "..." or hermes profile describe | | Model and provider | Model picker | coder config set model