Integration
Give Hermes social media superpowers
Hermes remembers across sessions, so its model of how you write is not rebuilt every conversation. That pairs unusually well with a publisher: the agent that learns your voice is also the one that sends it.
Nous Research's open-source agent, with persistent memory and a skills system that compounds over time.
Setup
- 1
Connect your accounts in AttentionPilot
Sign up, connect the networks you want, and check they show as active. Hermes can only publish where you have already granted access.
- 2
Create an API key
One key per agent, from the API keys page. Keys are stored as hashes and shown once. Revoking one cuts that agent off and nothing else.
- 3
Add AttentionPilot to ~/.hermes/config.yaml
AttentionPilot is an HTTP MCP server with a bearer token, which Hermes supports directly — no wrapper process to run.
Config lives in ~/.hermes/config.yaml.
mcp_servers:
attentionpilot:
url: "https://attentionpilot.com/api/mcp"
headers:
Authorization: "Bearer pilot_your_key_here"Reload with /reload-mcp inside a chat after editing the file, or Hermes will keep using the config it started with.
Then just ask
Hermes gets three tools: see what is connected, publish or schedule, and read back how each network went.
- “Post this to X and Bluesky at 9am tomorrow”
- “Draft a LinkedIn version of what I posted this morning”
- “Queue these three ideas across everything”
- “Did anything fail to publish this week?”
It will tell you what it is about to send and to which accounts. If a network rejects the post — a caption over the limit, an expired token — you get that network's error, and the other 9 still go out.
No MCP? Use the skill
AttentionPilot ships a Markdown skill file describing the REST API and the rules an agent should follow before publishing anything. Point Hermes at it and set one environment variable.
skills/attentionpilot-social/SKILL.md
PILOT_API_KEY=pilot_…
https://attentionpilot.com/api/v1/accounts
https://attentionpilot.com/api/v1/posts