Hermes BibleUnofficial Docs
← All docs Docs / Core Features

MCP (Model Context Protocol)

MCP lets Hermes Agent connect to external tool servers so the agent can use tools that live outside Hermes itself — GitHub, databases, file systems, browser sta

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/mcp

MCP lets Hermes Agent connect to external tool servers so the agent can use tools that live outside Hermes itself — GitHub, databases, file systems, browser sta

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. What MCP gives you
  2. Quick start
  3. Catalog: one-click install for Nous-approved MCPs
  4. Tool selection at install time
  5. Trust model
  6. Manifest version compatibility
  7. Runtime ${ENV_VAR} substitution
  8. Updating tool selection later
  9. Updating the catalog manifest
  10. Two kinds of MCP servers
  11. Stdio servers
  12. HTTP servers
  13. OAuth-authenticated HTTP servers
  14. mTLS / client certificates

Section map

What MCP gives you

Maps what mcp gives you to the Core Features documentation path, with the source page reserved for exact commands and updates.

Quick start

Maps quick start to the Core Features documentation path, with the source page reserved for exact commands and updates.

Catalog: one-click install for Nous-approved MCPs

Maps catalog: one-click install for nous-approved mcps to the Core Features documentation path, with the source page reserved for exact commands and updates.

Tool selection at install time

Maps tool selection at install time to the Core Features documentation path, with the source page reserved for exact commands and updates.

Trust model

Maps trust model to the Core Features documentation path, with the source page reserved for exact commands and updates.

Manifest version compatibility

Maps manifest version compatibility to the Core Features documentation path, with the source page reserved for exact commands and updates.

Runtime ${ENV_VAR} substitution

Maps runtime ${env_var} substitution to the Core Features documentation path, with the source page reserved for exact commands and updates.

Updating tool selection later

Maps updating tool selection later to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features 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: What MCP gives you, Quick start, Catalog: one-click install for Nous-approved MCPs, Tool selection at install time, Trust model. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: model, context, protocol, connect, external. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for mcp (model context protocol) before applying exact upstream commands.

Verify firstWhat MCP gives you

Open the source anchor for What MCP gives you 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 Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for What MCP gives you; 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 Quick start 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

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

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