---
title: "Hermes Agent integration with Bolta"
description: "Connect Hermes Agent to Bolta with one mcp_servers entry in config.yaml. Draft posts from Telegram or the terminal and approve them in Bolta before anything publishes."
canonical_url: "https://bolta.ai/integrations/hermes-agent"
markdown_url: "https://bolta.ai/integrations/hermes-agent.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Hermes Agent integration with Bolta

Source: https://bolta.ai/integrations/hermes-agent
Last updated: 2026-11-21

Connect Hermes Agent to Bolta with one mcp\_servers entry in config.yaml. Draft posts from Telegram or the terminal and approve them in Bolta before anything publishes.

## Summary

Draft and review social posts from Telegram, Slack or your terminal

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Message your Hermes bot in Telegram or Discord with a post idea and get a draft saved to Bolta review without opening a laptop
- Let Hermes cron run a Monday planning pass and message you the plan, with Bolta holding every draft for approval
- Keep Hermes's cross-session memory for tone notes, while Bolta's voice profile keeps the actual drafts on brand
- Run Hermes from the terminal on a home server and ask it for a weekly read of your account analytics
- Have Hermes check the Bolta inbox each morning and tell you what is waiting, then approve only what you pick
- Limit the Bolta tools Hermes sees to read and draft, so a self-hosted agent never has a publish tool in reach

## Limitations and boundaries

- Confirmed from the Hermes docs: Hermes reads remote MCP servers from an mcp\_servers block in ~/.hermes/config.yaml, with a url and a headers map for a Bearer key. Bolta's server is https://mcp.bolta.ai/mcp and takes a key that starts with bolta\_sk\_.
- Not confirmed: we have not run this end to end in Hermes Agent. The OAuth option (auth: oauth) has never been tried against Bolta, so this page leads with the API key.
- Not confirmed: the skill install command against Bolta's skills repo, and the exact tool names Hermes shows for Bolta (expected to start with mcp\_bolta\_). If a step differs on your machine, trust what Hermes shows you.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Install Hermes Agent

On macOS, Linux or WSL2 run: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash. On Windows use the PowerShell installer or the desktop app from the Hermes website. Then run hermes setup for the full wizard. The Hermes install page also lists hermes setup --portal as a faster path that signs you in to Nous and sets Nous as the provider, which you only want if you plan to use that provider.

## Create a Bolta API key

In Bolta open Settings, then API Keys, and create a key. It starts with bolta\_sk\_. Choose the permissions you want it to have, copy it once and keep it private. A key belongs to one organization.

## Open the Hermes config file

Open ~/.hermes/config.yaml in a text editor. If the file has no mcp\_servers block yet, you will add one in the next step.

## Add Bolta under mcp\_servers

Add an entry named bolta with url: "https://mcp.bolta.ai/mcp" and a headers block containing Authorization: "Bearer bolta\_sk\_your\_key". Save the file. Do not commit this file anywhere public, it now holds your key.

## Optional: use OAuth instead of a key

Hermes also supports auth: oauth in place of the headers block, then hermes mcp login bolta, which walks you through signing in. This has not been tested with Bolta. If it fails, go back to the API key.

## Check the connection

In a Hermes chat type /reload-mcp, or in a terminal run hermes mcp test bolta. You should see Bolta's tools listed. The Hermes docs name MCP tools with an mcp\_ prefix and the server name, so expect names like mcp\_bolta\_save\_post.

## Add the Bolta skill

Run hermes skills install boltaai/bolta-skills/skills/bolta so Hermes knows Bolta's playbooks for drafting and review. You can run hermes skills inspect on it first to read it. The MCP connection works without the skill, the skill just gives better first answers.

## Run a read-only test

Ask Hermes: "List my Bolta workspaces and accounts." Check that it names the right brands. If none are connected, ask it for a Bolta connect link and add an account first.

## Ask for your first draft

Try: "Draft three LinkedIn posts about our launch in our brand voice and send them to review." Open Bolta to read them. They stay drafts until you approve each one yourself.

## The mcp\_servers block, copy and paste

Hermes is set up by editing a YAML file, not by clicking a connector. This is the shape the Hermes docs describe for a remote server with a Bearer key. Under mcp\_servers, add bolta with url set to https://mcp.bolta.ai/mcp and a headers map holding Authorization with the value Bearer followed by your bolta\_sk\_ key. Save, then type /reload-mcp in a chat to pick up the edit without restarting. Keep the key out of version control. If you keep your Hermes config in a dotfiles repo, store the key somewhere private and rotate it in Bolta under Settings, then API Keys if it ever leaks.

## Run Bolta from your chat apps

The reason to use Hermes rather than a desktop assistant is that it can sit on a server and answer in the apps you already use. Hermes lists Telegram, Discord, Slack, WhatsApp and Signal among the apps it can answer in. Which ones you enable is set in Hermes, not Bolta. A draft you ask for in chat is saved in Bolta, so review happens in Bolta and not in the chat thread. Anyone who can message your Hermes bot can ask it things. Restrict who can reach it in Hermes before connecting a Bolta key with publish permission.

## Tool names and keeping the list short

Hermes prefixes MCP tools with mcp\_ and the server name, so a tool called save-post should appear as something like mcp\_bolta\_save\_post. That prefix rule comes from the Hermes docs and we have not seen the exact list on a live install, so check hermes mcp test bolta. The Hermes docs also describe tools.include and tools.exclude settings for a server. Use them to leave Bolta's read and draft tools on and the approve and publish tools off. Entries are exact names or patterns, and include wins if you set both. hermes mcp configure bolta reopens a checklist of the tools if you would rather tick them. Safe to leave on: list-workspaces, list-accounts; Needs your yes: approve-many-posts | Safe to leave on: list-inbox-items, get-account-analytics; Needs your yes: publish-post | Safe to leave on: save-post, plan; Needs your yes: confirm-plan, activate-routine

## Do you need the Bolta skill too?

No. The MCP connection is what lets Hermes call Bolta. The skill is a folder of instructions that teaches Hermes how Bolta works, such as checking posting rules before saving a draft. Hermes installs skills with hermes skills install owner/repo/path, and Bolta's skill is in the boltaai/bolta-skills repo under skills/bolta. We have not run that install against this repo, so read the skill with hermes skills inspect before you install it and trust what Hermes reports.

## Hermes memory and Bolta's voice profile do different jobs

Hermes keeps memory across sessions, so it can remember that you prefer short openings or that a product name has a special spelling. That memory lives on your Hermes install. Bolta's voice profile lives in your Bolta workspace and is what get-voice-context reads before a draft. Keeping the real voice in Bolta means a draft sounds the same whether you ask from Telegram, the terminal or another app.

## Who can message your bot also reaches Bolta

A self-hosted agent on a chat app is only as private as the list of people allowed to talk to it. Set who may message your Hermes bot in Hermes before you add a Bolta key. Create a Bolta key with only the permissions you need. A drafting key does not need to publish. If a key may have been shared, revoke it under Settings, then API Keys in Bolta and add a new one to config.yaml.

## A cautious first week with Hermes and Bolta

1. Day one: read only: Connect, run hermes mcp test bolta, and ask for your workspaces and accounts. Change nothing. 2. Days two and three: drafts only: Ask for drafts and read each one in Bolta. Keep the approve and publish tools off in tools.exclude while you learn how it answers. 3. Later: one routine: Ask Hermes to plan one routine, read the plan, and confirm it. Decide separately whether to turn it on.

## What is Hermes Agent, and is it the same as the Hermes models?

Hermes Agent is an open-source agent from Nous Research that you install and run yourself. It is not the same thing as the Hermes language models, which are models, not an agent program. This page is about the agent.

## Does Hermes Agent work with Bolta over MCP?

It should, because Hermes supports remote MCP servers and Bolta runs one at https://mcp.bolta.ai/mcp. We have not run it end to end in Hermes yet, which is why this page carries a caveat.

## Should I use an API key or OAuth to connect Bolta to Hermes?

Use the API key. Hermes supports OAuth for MCP servers, but it has not been tested against Bolta. If you try it and it works, the key is still the fallback.

## Where do I put the Bolta server in Hermes?

In ~/.hermes/config.yaml, under an mcp\_servers block, as an entry named bolta with the url and an Authorization header. Then type /reload-mcp in a chat.

## Do I need the Bolta skill as well as the MCP connection?

No. The connection is enough to call Bolta's tools. The skill adds instructions so Hermes handles things like posting rules in the right order. We have not tested the skill install in Hermes.

## Can Hermes post to my accounts without my approval?

Bolta's rule is that nothing is approved, scheduled or published until you say yes, and a draft Hermes saves stays in review. We have not tested this from Hermes, so a key with narrower permissions and a shorter tool list is a sensible second layer.

## Can Hermes draft posts on a schedule and message me in Telegram or Slack?

Hermes has a built-in scheduler and can answer in chat apps, so the idea fits. The scheduling and chat delivery are Hermes features, and we have not tested that combination with Bolta. The drafts it saves still wait in Bolta review.

## Hermes cron or a Bolta routine: which should I schedule with?

Use Hermes cron if you want the result sent to a chat app and your Hermes stays running. Use a Bolta routine if the schedule should keep going when Hermes is off. A routine is saved switched off and needs a separate yes to start.

## Why do the Bolta tools show up as mcp\_bolta\_...?

Hermes names MCP tools with the server name in front. Hyphens in a tool name are expected to become underscores, so save-post would appear as mcp\_bolta\_save\_post. Run hermes mcp test bolta to see the real list.

## One connection covers which brands?

A Bolta API key belongs to one organization, so it reaches the brands in that organization. Ask Hermes to list your workspaces first, and name the brand when you ask for a draft.

## How do I limit which Bolta tools Hermes can call?

The Hermes docs describe tools.include and tools.exclude settings for a server, and hermes mcp configure bolta opens a checklist. Leave read and draft tools on and the approve and publish tools off. We have not tested these settings with Bolta.

## What do I do if Hermes says the server is unreachable?

Check the url is exactly https://mcp.bolta.ai/mcp, check the indentation under mcp\_servers, then run hermes mcp test bolta. If the test passes but chat still has no Bolta tools, type /reload-mcp.

## hermes mcp test bolta says the server is unreachable.

Check the url is exactly https://mcp.bolta.ai/mcp with no trailing text, and that the machine running Hermes can reach the internet. A YAML indentation slip under mcp\_servers is a common cause, so check the spacing of that block first.

## Bolta tools are missing after I edited config.yaml.

Hermes does not reread the file on its own. Type /reload-mcp in the chat, or restart Hermes, then run hermes mcp test bolta again.

## I get an unauthorized or 401 error.

The key is wrong, was pasted with a line break, or was revoked. Create a fresh key under Settings, then API Keys in Bolta and paste it after the word Bearer and one space.

## Hermes sees my workspace but no accounts.

The key belongs to one organization and the brand may not be connected or included. Ask Hermes for a Bolta connect link and connect the account, then list accounts again.

## auth: oauth never finishes signing in.

OAuth against Bolta has not been tested from Hermes. Remove auth: oauth, use the headers block with an API key instead, and run /reload-mcp.

## Hermes Agent is not the Hermes models, and not OpenClaw

Hermes Agent is an agent program from Nous Research that you install and run. It is a separate thing from the Hermes language models. OpenClaw is a different agent.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/openclaw](https://bolta.ai/integrations/openclaw)
- [Related page: /integrations/mcp](https://bolta.ai/integrations/mcp)
- [Related page: /integrations/claude-code](https://bolta.ai/integrations/claude-code)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Hermes Agent official website](https://hermes-agent.nousresearch.com/docs)
