Integrations
التكاملات المتاحة
What this page is, and what it holds.
This page covers Integrations. You will use hermes model and hermes tools here; about 6 minutes to read. Any MCP server you add can see your data and act for you. Run only what you can trace, and start with the fewest tools.
Outcomes taken from this page, not a template.
- Understand what MCP is and when you need it.
- Run
hermes modelandhermes toolsand understand what happens next. - Read the table and take only the row that applies to you.
- Set
FIRECRAWL_API_URLin the right place.
Exactly as they appear in Hermes.
hermes modelhermes tools
FIRECRAWL_API_URLHASS_TOKEN
Jump to the part you need.
Nothing summarised away.
The documentation body below is reproduced from the official source so commands and identifiers stay exact. Each section carries a short note describing what it contains.
Hermes Agent connects to external systems for AI inference, tool servers, IDE workflows, programmatic access, and more. These integrations extend what Hermes can do and where it can run.
AI Providers & Routing
Commands you type in a terminal. Understand what one does before copying it. Commands here: hermes model.
Hermes supports multiple AI inference providers out of the box. Use hermes model to configure interactively, or set them in config.yaml.
- AI Providers — OpenRouter, Anthropic, OpenAI, Google, and any OpenAI-compatible endpoint. Hermes auto-detects capabilities like vision, streaming, and tool use per provider.
- Provider Routing — Fine-grained control over which underlying providers handle your OpenRouter requests. Optimize for cost, speed, or quality with sorting, whitelists, blacklists, and explicit priority ordering.
- Fallback Providers — Automatic failover to backup LLM providers when your primary model encounters errors. Includes primary model fallback and independent auxiliary task fallback for vision, compression, and web extraction.
Tool Servers (MCP)
Explains the idea itself. Read it slowly; the later sections build on it.
- MCP Servers — Connect Hermes to external tool servers via Model Context Protocol. Access tools from GitHub, databases, file systems, browser stacks, internal APIs, and more without writing native Hermes tools. Supports both stdio and SSE transports, per-server tool filtering, and capability-aware resource/prompt registration.
Web Search Backends
A lookup table. Do not read it all; find the row that applies to you. Commands here: hermes tools.
The web_search and web_extract tools support eight backend providers, configured via config.yaml or hermes tools:
| Backend | Env Var | Search | Extract | Crawl |
|---|---|---|---|---|
| Firecrawl (default) | FIRECRAWL_API_KEY | ✔ | ✔ | ✔ |
| SearXNG | SEARXNG_URL | ✔ | — | — |
| Brave (free tier) | BRAVE_SEARCH_API_KEY | ✔ | — | — |
| DuckDuckGo (ddgs) | _(none)_ | ✔ | — | — |
| Tavily | TAVILY_API_KEY | ✔ | ✔ | ✔ |
| Exa | EXA_API_KEY | ✔ | ✔ | — |
| Parallel | PARALLEL_API_KEY | ✔ | ✔ | — |
| xAI | XAI_API_KEY | ✔ | — | — |
Quick setup example:
web:
backend: firecrawl # firecrawl | searxng | brave-free | ddgs | tavily | exa | parallel | xaiIf web.backend is not set, the backend is auto-detected from whichever API key is available. Self-hosted Firecrawl is also supported via FIRECRAWL_API_URL.
Browser Automation
Explains the idea itself. Read it slowly; the later sections build on it.
Hermes includes full browser automation with multiple backend options for navigating websites, filling forms, and extracting information:
- Browserbase — Managed cloud browsers with anti-bot tooling, CAPTCHA solving, and residential proxies
- Browser Use — Alternative cloud browser provider
- Local Chromium-family CDP — Connect to your running Chrome, Brave, Chromium, or Edge browser using
/browser connect - Local Chromium — Headless local browser via the
agent-browserCLI
See Browser Automation for setup and usage.
Voice & TTS Providers
A lookup table. Do not read it all; find the row that applies to you.
Text-to-speech and speech-to-text across all messaging platforms:
| Provider | Quality | Cost | API Key |
|---|---|---|---|
| Edge TTS (default) | Good | Free | None needed |
| ElevenLabs | Excellent | Paid | ELEVENLABS_API_KEY |
| OpenAI TTS | Good | Paid | VOICE_TOOLS_OPENAI_KEY |
| MiniMax | Good | Paid | MINIMAX_API_KEY |
| xAI TTS | Good | Paid | XAI_API_KEY |
| NeuTTS | Good | Free | None needed |
Speech-to-text supports eight providers: local faster-whisper (free, runs on-device), a local command wrapper, Groq, OpenAI Whisper API, Mistral, xAI, ElevenLabs Scribe, and DeepInfra. Voice message transcription works across Telegram, Discord, WhatsApp, and other messaging platforms. See Voice & TTS and Voice Mode for details.
IDE & Editor Integration
Explains the idea itself. Read it slowly; the later sections build on it.
- IDE Integration (ACP) — Use Hermes Agent inside ACP-compatible editors such as VS Code, Zed, and JetBrains. Hermes runs as an ACP server, rendering chat messages, tool activity, file diffs, and terminal commands inside your editor.
Programmatic Access
Explains the idea itself. Read it slowly; the later sections build on it.
- API Server — Expose Hermes as an OpenAI-compatible HTTP endpoint. Any frontend that speaks the OpenAI format — Open WebUI, LobeChat, LibreChat, NextChat, ChatBox — can connect and use Hermes as a backend with its full toolset.
Memory & Personalization
Explains the idea itself. Read it slowly; the later sections build on it.
- Built-in Memory — Persistent, curated memory via
MEMORY.mdandUSER.mdfiles. The agent maintains bounded stores of personal notes and user profile data that survive across sessions. - Memory Providers — Plug in external memory backends for deeper personalization. Eight providers are supported: Honcho (dialectic reasoning), OpenViking (tiered retrieval), Mem0 (cloud extraction), Hindsight (knowledge graphs), Holographic (local SQLite), RetainDB (hybrid search), ByteRover (CLI-based), and Supermemory.
Messaging Platforms
A lookup table. Do not read it all; find the row that applies to you.
Hermes runs as a gateway bot on 27+ messaging platforms, all configured through the same gateway subsystem:
- Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Mattermost, Email, SMS, DingTalk, Feishu/Lark, WeCom, WeCom Callback, Weixin, BlueBubbles, Buzz, QQ Bot, Yuanbao, Home Assistant, Microsoft Teams, Microsoft Teams Meetings, Microsoft Graph Webhook, Google Chat, LINE, ntfy, SimpleX, Open WebUI, Webhooks
See the Messaging Gateway overview for the platform comparison table and setup guide.
Quick connect links
The big platforms have a canonical "create your bot/app" URL, and some accept parameters that pre-open the right form. Skip the console-hunting and go straight there:
| Platform | Direct link | What it opens |
|---|---|---|
| Telegram | t.me/BotFather ↗ | Chat with BotFather — send /newbot to mint a bot token |
| Discord | discord.com/developers/applications?new_application=true ↗ | Developer Portal with the New Application dialog pre-opened |
| Slack | api.slack.com/apps?new_app=1 ↗ | The Create New App dialog — pick From an app manifest and paste the manifest hermes slack manifest --agent-view generates |
| LINE | developers.line.biz/console ↗ | LINE Developers Console for creating a Messaging API channel |
| Feishu/Lark | open.feishu.cn/app ↗ | Feishu open-platform console for creating a custom app |
Each platform's setup page walks through what to do once you're there.
Collaboration Workspaces
Explains the idea itself. Read it slowly; the later sections build on it.
- Buzz — Block's Nostr-based human+agent workspace. Three integration paths: Buzz Desktop spawns Hermes as a managed ACP runtime, the
buzz-acprelay bridge hosts a Hermes identity server-side, or the native gateway platform joins Buzz channels with full Hermes memory/skills/approvals/cron. The overview page compares all three.
Home Automation
Settings you configure once. Change one at a time so you can see what each does. Set HASS_TOKEN in your environment, not in the chat.
- Home Assistant — Control smart home devices via four dedicated tools (
ha_list_entities,ha_get_state,ha_list_services,ha_call_service). The Home Assistant toolset activates automatically whenHASS_TOKENis configured.
Plugins
Explains the idea itself. Read it slowly; the later sections build on it.
- Plugin System — Extend Hermes with custom tools, lifecycle hooks, and CLI commands without modifying core code. Plugins are discovered from
~/.hermes/plugins/, project-local.hermes/plugins/, and pip-installed entry points. - Build a Plugin — Step-by-step guide for creating Hermes plugins with tools, hooks, and CLI commands.
Training & Evaluation
Explains the idea itself. Read it slowly; the later sections build on it.
- Batch Processing — Run the agent across hundreds of prompts in parallel, generating structured ShareGPT-format trajectory data for training data generation or evaluation.
4 questions answered by this page alone.
Every option is a real identifier from the Hermes documentation. The wrong ones are real too, just from other pages.