native-mcp

Connect external MCP servers to Hermes Agent and register their tools as native actions.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill native-mcp-jkhyro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill native-mcp-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of wiring external MCP servers into Hermes Agent by turning their tools into native, directly callable agent tools. It helps you avoid bridge CLIs and manual tool shims while keeping integrations discoverable at startup.

Core Features & Use Cases

  • Native tool registration: Discovers tools from configured MCP servers and exposes them alongside built-in Hermes tools.
  • Flexible transport support: Works with local stdio servers and remote HTTP or StreamableHTTP servers.
  • Secure operation: Filters subprocess environment variables, redacts credential-like values from errors, and supports per-server sampling controls.
  • Use case: Connect filesystem, GitHub, database, or API MCP servers once in config, then use their capabilities in every Hermes conversation automatically.

Quick Start

Add your MCP server to Hermes Agent's mcp_servers configuration and restart the agent so its tools are discovered and made available automatically.

Frequently Asked Questions about native-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect external MCP servers to Hermes Agent as native tools?

To connect external MCP servers to Hermes Agent, add your server configurations to the mcp_servers section in ~/.hermes/config.yaml and restart the agent. The Skill automatically discovers their tools and registers them as native, directly callable actions alongside built-in Hermes tools.

Does MCP tool discovery support both local stdio and remote HTTP servers?

MCP tool discovery supports both local stdio servers and remote HTTP or StreamableHTTP servers. This flexible transport support allows you to integrate filesystems, GitHub, databases, and APIs directly into Hermes Agent conversations.

What security filtering is applied when integrating MCP servers?

Security filtering for MCP server integration includes filtering subprocess environment variables and redacting credential-like values from error messages. It also supports per-server sampling controls to manage how external tools interact with your agent.

Why do I need the mcp Python package for Hermes Agent integrations?

The mcp Python package is required to enable native MCP tool registration and communication across stdio and HTTP transports. Without this optional dependency installed, Hermes Agent cannot discover external tools or establish reconnection controls for configured servers.

Can I use filesystem and database MCP servers without writing manual tool shims?

You can use filesystem, database, GitHub, and API MCP servers without manual tool shims or bridge CLIs. Once configured in ~/.hermes/config.yaml, the Skill discovers their capabilities at startup and exposes them automatically in every Hermes conversation.

What happens when a remote HTTP MCP server connection drops during an agent task?

When a remote HTTP MCP server connection drops, the Skill applies automatic reconnection logic to restore the link and maintain tool availability. This ensures registered external tools remain accessible without requiring a manual agent restart.