Skip to content
China Explained

Integrations

Integrations

Section titled “Integrations”

Hermes can connect to more systems through MCP, API server, OpenAI-compatible frontends, browser tools, media tools, and provider gateways. Integrations are valuable because they let Hermes use existing tools. They are risky because they expand what a local agent can affect.

A simple rule: understand the local workflow before exposing it as an interface.

Write the contract first

Section titled “Write the contract first”

Whether the integration is an MCP server, API server, webhook, or browser tool, answer these questions first:

QuestionImpact
Who calls itAuthentication, authorization, audit.
What can be calledTool list, input schema, output format.
How long it may runTimeout, queue, concurrency, cost.
What it can accessFiles, network, credentials, external APIs.
What happens on failureRetry, rollback, user-visible error.
How it is observedLogs, traces, metrics, request IDs.

If these answers are unclear, integration will only amplify uncertainty.

MCP is for existing tool servers

Section titled “MCP is for existing tool servers”

MCP is useful for connecting Hermes to external tool servers: internal queries, knowledge bases, code indexes, browser automation, or business tools. The key question is not whether Hermes can connect, but which tools it sees after connecting.

Control:

  • Expose only the tools needed for the current task.
  • Document tool inputs and outputs.
  • Add human confirmation to high-risk tools.
  • Separate read-only tools from write tools.
  • Record server version, source, and auth method.

Do not expose a large MCP server wholesale just because discovery works. The wider the tool surface, the higher the misuse and debugging cost.

API server should wrap known workflows

Section titled “API server should wrap known workflows”

Hermes API server and OpenAI-compatible behavior can support existing frontends, internal platforms, or automation systems. It should not mean exposing the whole local agent directly to the network.

A better pattern is to wrap a small number of known workflows:

POST /draft-release-notes
Input: repo, version, merged_pr_range
Output: markdown draft
Tools: read-only GitHub access
Human step: approve before publish

The more specific the interface, the easier it is to narrow permissions and explain failures.

Browser and web tools need prompt-injection discipline

Section titled “Browser and web tools need prompt-injection discipline”

Web pages and browser state often mix facts, ads, user content, stale instructions, and malicious instructions. When Hermes reads a page, the page is evidence, not a system instruction.

For research or documentation, keep:

  • URL.
  • Access date.
  • Which facts came from which page.
  • Which conclusions are inferences.
  • What was not verified.

For logged-in pages, also consider cookies, account permissions, and accidental clicks. When a read-only API can answer the question, prefer it over a logged-in browser for high-impact actions.

Media tools are for observation, not final review

Section titled “Media tools are for observation, not final review”

Vision, image generation, TTS, voice, and transcription let Hermes work with screenshots, audio, and multimedia inputs. Media models can misread details, and generated content may have copyright, brand, or factual issues.

For high-impact work, keep:

  • Original screenshot, audio, or image path.
  • Transcript or recognition output.
  • Generation prompt and model.
  • Human confirmation record.

Media tools are useful for drafts and observation. They should not replace final review.

Safer defaults

Section titled “Safer defaults”
ScenarioDefault recommendation
Internal tool lookupStart read-only.
File or code writesLimit directories and keep diffs.
Network API callsAdd timeout, budget, and logs.
Sending messagesDraft first, send after human confirmation.
Production changeDo not let the agent execute directly without strict approval and rollback.
Section titled “Related pages”

References

Section titled “References”