Academy → Integrations and ProvidersOfficial documentation · Arabic guidance

Integrations

التكاملات المتاحة

Intermediate6 min readLesson 44 questions✓ 2026-08-18
Before you read

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.

13sections
1code examples
3tables
2commands
967source words
What you will be able to do

Outcomes taken from this page, not a template.

  • Understand what MCP is and when you need it.
  • Run hermes model and hermes tools and understand what happens next.
  • Read the table and take only the row that applies to you.
  • Set FIRECRAWL_API_URL in the right place.
Identifiers you will meet

Exactly as they appear in Hermes.

Commands
  • hermes model
  • hermes tools
Environment variables
  • FIRECRAWL_API_URL
  • HASS_TOKEN
Page map

Jump to the part you need.

  1. 01AI Providers & Routing
  2. 02Tool Servers (MCP)
  3. 03Web Search Backends
  4. 04Browser Automation
  5. 05Voice & TTS Providers
  6. 06IDE & Editor Integration
  7. 07Programmatic Access
  8. 08Memory & Personalization
  9. 09Messaging Platforms
  10. 10Collaboration Workspaces
  11. 11Home Automation
  12. 12Plugins
  13. 13Training & Evaluation
The full official page

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:

BackendEnv VarSearchExtractCrawl
Firecrawl (default)FIRECRAWL_API_KEY✔✔✔
SearXNGSEARXNG_URL✔——
Brave (free tier)BRAVE_SEARCH_API_KEY✔——
DuckDuckGo (ddgs)_(none)_✔——
TavilyTAVILY_API_KEY✔✔✔
ExaEXA_API_KEY✔✔—
ParallelPARALLEL_API_KEY✔✔—
xAIXAI_API_KEY✔——

Quick setup example:

YAML2 lines
web:
  backend: firecrawl    # firecrawl | searxng | brave-free | ddgs | tavily | exa | parallel | xai

If 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-browser CLI

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:

ProviderQualityCostAPI Key
Edge TTS (default)GoodFreeNone needed
ElevenLabsExcellentPaidELEVENLABS_API_KEY
OpenAI TTSGoodPaidVOICE_TOOLS_OPENAI_KEY
MiniMaxGoodPaidMINIMAX_API_KEY
xAI TTSGoodPaidXAI_API_KEY
NeuTTSGoodFreeNone 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.md and USER.md files. 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:

See the Messaging Gateway overview for the platform comparison table and setup guide.

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:

PlatformDirect linkWhat it opens
Telegramt.me/BotFather ↗Chat with BotFather — send /newbot to mint a bot token
Discorddiscord.com/developers/applications?new_application=true ↗Developer Portal with the New Application dialog pre-opened
Slackapi.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
LINEdevelopers.line.biz/console ↗LINE Developers Console for creating a Messaging API channel
Feishu/Larkopen.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-acp relay 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 when HASS_TOKEN is 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.
Knowledge check

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.

1. In this lesson's table, what is the “Env Var” for “DuckDuckGo (ddgs)”?
2. Which of these environment variables actually appears in this lesson?
3. Which of these headings does not appear in this lesson?
4. Which configuration key appears in this lesson's examples?