native-mcp

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

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/dawsonblock/HERMY --skill native-mcp-dawsonblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/dawsonblock/HERMY/tree/main/hermes-agent-2026.4.23/skills/mcp/native-mcp
Command: npx skills add https://github.com/dawsonblock/HERMY --skill native-mcp-dawsonblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Built-in MCP client that connects to external MCP servers at startup, discovers their tools, and registers them as native Hermes Agent tools. Supports stdio and HTTP transports with automatic reconnection, security filtering, and zero-config tool injection.

Core Features & Use Cases

  • Auto-discovery of MCP servers at Hermes Agent startup.
  • Supports stdio and HTTP MCP transports with automatic reconnection.
  • Secure environment handling with credential filtering.
  • Zero-config tool injection into Hermes toolsets for immediate availability.
  • Use cases: extend Hermes with external capabilities like GitHub, filesystem, time, etc.

Quick Start

Install the MCP SDK in your environment and configure mcp_servers in your ~/.hermes/config.yaml, then restart Hermes Agent to automatically discover tools.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I auto-discover and register MCP server tools in Hermes Agent?

Hermes Agent connects to external MCP servers at startup to automatically discover and register their tools as native Hermes Agent tools. It applies MCP auto-discovery across both stdio and HTTP transports with automatic reconnection for continuous tool availability.

What is the difference between stdio and HTTP transport for MCP tool discovery?

MCP tool discovery supports both stdio and HTTP transports to connect external MCP servers to Hermes Agent. Both transport mechanisms include automatic reconnection and security filtering to maintain continuous tool availability across conversations.

Do I need to install the MCP Python package to use MCP auto-discovery?

Yes, MCP auto-discovery requires installing the optional mcp Python package in your environment. You must also configure your mcp_servers in the ~/.hermes/config.yaml file and restart Hermes Agent to trigger the automatic tool injection process.

How does Hermes Agent handle credentials and security when connecting to MCP servers?

Hermes Agent applies secure environment handling with credential filtering when connecting to external MCP servers. This security filtering ensures tools are safely registered and remain available in every conversation without exposing sensitive credentials.

Can I extend Hermes Agent with external capabilities like GitHub and filesystem tools?

You can extend Hermes Agent with external capabilities like GitHub, filesystem, and time tools by connecting to external MCP servers. These external capabilities are automatically discovered and injected as native Hermes Agent tools with zero configuration.

Why are my MCP tools not showing up after configuring mcp_servers in Hermes?

If MCP tools are not showing up, verify the optional mcp Python package is installed and Hermes Agent has been restarted. The auto-discovery process connects to external MCP servers at startup, so a restart is required to register newly configured tools.