native-mcp

Connect to MCP servers and register their tools into Hermes toolsets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes needs seamless access to tools exposed by external MCP servers; native-mcp provides a built-in MCP client that automatically discovers and registers those tools as native Hermes tools, eliminating the need for manual bridging. Security filtering and automatic reconnection are supported.

Core Features & Use Cases

  • Auto-discovery of MCP servers and their tools
  • Automatic registration with the naming convention mcp_{server}_{tool}, and injection into all Hermes toolsets
  • Supports stdio and HTTP transports with automatic reconnection
  • Security filtering of environment variables and credentials
  • Zero-config tool injection

Quick Start

Configure Hermes to connect to an MCP server in the config file and restart the agent to begin tool discovery and injection.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I integrate MCP server tools into Hermes automatically?

To integrate MCP server tools into Hermes, configure your MCP servers in the ~/.hermes/config.yaml file. The native-mcp client discovers available tools at startup and auto-registers them under the mcp_{server}_{tool} naming convention for immediate injection into all Hermes toolsets.

What naming convention does Hermes use for auto-registered MCP tools?

MCP tools are registered using the mcp_{server}_{tool} naming convention. This standardized format ensures that every tool discovered from connected MCP servers is uniquely identified and seamlessly injected into all available Hermes toolsets.

Do I need to manually configure tool bridging for stdio and HTTP MCP servers?

No manual bridging is required. The native-mcp client supports both stdio and HTTP transports with automatic reconnection, handling tool discovery and zero-config injection into Hermes natively without manual setup.

Does native-mcp filter sensitive credentials during MCP tool discovery?

Yes, the native-mcp client includes security filtering for environment variables and credentials. This prevents sensitive information from being exposed during the tool discovery and automatic registration process with external MCP servers.

What prerequisites are needed to enable MCP tool discovery in Hermes?

You need the MCP Python package installed and a configured ~/.hermes/config.yaml file containing your mcp_servers definitions. Once configured, restarting the agent triggers automatic discovery and registration.

How does Hermes handle automatic reconnection for MCP servers?

Restarting the Hermes agent triggers the native-mcp client to re-initiate tool discovery. It automatically reconnects to configured MCP servers via stdio or HTTP transports and re-registers all available tools into the Hermes toolsets.