Hermes BibleUnofficial Docs
← All docs Docs / Reference

MCP Config Reference

This page is the compact reference companion to the main MCP docs. For conceptual guidance, see: MCP (Model Context Protocol) Use MCP with Hermes Root config sh

Reference
Section
Reference
Source
hermesbible.com/docs/reference/mcp-config-reference

This page is the compact reference companion to the main MCP docs. For conceptual guidance, see: MCP (Model Context Protocol) Use MCP with Hermes Root config sh

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Root config shape
  2. Server keys
  3. tools policy keys
  4. Filtering semantics
  5. include
  6. exclude
  7. Precedence
  8. Utility-tool policy
  9. Disable resources
  10. Disable prompts
  11. Capability-aware registration
  12. enabled: false
  13. Empty result behavior
  14. Example configs

Section map

Root config shape

Maps root config shape to the Reference documentation path, with the source page reserved for exact commands and updates.

Server keys

Maps server keys to the Reference documentation path, with the source page reserved for exact commands and updates.

tools policy keys

Maps tools policy keys to the Reference documentation path, with the source page reserved for exact commands and updates.

Filtering semantics

Maps filtering semantics to the Reference documentation path, with the source page reserved for exact commands and updates.

include

Maps include to the Reference documentation path, with the source page reserved for exact commands and updates.

exclude

Maps exclude to the Reference documentation path, with the source page reserved for exact commands and updates.

Precedence

Maps precedence to the Reference documentation path, with the source page reserved for exact commands and updates.

Utility-tool policy

Maps utility-tool policy to the Reference documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Reference doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Root config shape, Server keys, tools policy keys, Filtering semantics, include. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: config, reference, compact, companion, docs.. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitReference documentation

Use when you need orientation for mcp config reference before applying exact upstream commands.

Verify firstRoot config shape

Open the source anchor for Root config shape and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Reference, then open the linked source page for exact current syntax.
  2. Start with the source section for Root config shape; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Server keys if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page