3
MCP Servers Plugins Webhooks Tools
Alan Wizemann edited this page 2026-04-27 13:00:18 +02:00

MCP Servers / Plugins / Webhooks / Tools

Four sidebar items that all extend what Hermes can do. Grouped here because the workflows are similar.

MCP Servers

Manage Model Context Protocol servers Hermes connects to. Two ways to add:

  • Curated presets — Filesystem, GitHub, Postgres, Slack, Linear, Sentry, Notion, Stripe, Puppeteer, Memory, Fetch, and more. Picking a preset fills in the command, args, and the env keys it needs.
  • Custom — stdio (command + args) or HTTP (URL + optional bearer auth).

Per-server detail view:

  • Enable / disable toggle.
  • Environment variable + header editor — written through HermesEnvService so existing comments and blanks are preserved.
  • Tool include / exclude filters (whitelist / blacklist what the server exposes).
  • Resources / prompts toggles.
  • Request and connect timeouts.
  • OAuth token detection and clearing.
  • Test Connection runs hermes mcp test and surfaces the discovered tool list inline.

A gateway-restart banner appears after config changes that require a reload.

MCP servers are stored in config.yaml under the mcp_servers key; the model is HermesMCPServer.

Plugins

Hermes plugins are git-cloned into ~/.hermes/plugins/. Scarf reads the directory directly for reliable state.

Operations:

  • Install via Git URL or owner/repo shorthand.
  • Update (pulls latest).
  • Remove.
  • Enable / disable.

Webhooks

Create, list, test-fire, and remove webhook subscriptions:

  • Endpoint URL, event filter, optional secret.
  • Test fire sends a synthetic event so you can verify the receiver before going live.
  • Detects the "platform not enabled" state and links to the gateway setup.

Tools

Enable / disable Hermes toolsets per platform.

  • Each platform (Telegram, Discord, Slack, etc.) gets its own toolset list.
  • Connectivity-aware platform menu: green / orange / grey / red dots match the gateway's reported state.
  • Toggling calls hermes tools enable/disable via context.runHermes.

Fixed in 1.6: all 13 platforms now appear here (was previously stuck on CLI only).

Credential Pools

(Same Configure section, related concept.) Per-provider credential rotation:

  • API key + OAuth flow handling. The OAuth flow does URL extraction → browser open → code paste; --type api-key is correctly inferred for direct API keys.
  • API keys are never stored in UI state — only the last 4 chars are previewed.
  • Strategy picker: fill_first / round_robin / least_used / random.

Last updated: 2026-04-25 — Scarf v2.5.0 (no MCP/Plugins/Webhooks/Tools changes since v2.0.1; refresh footer)