native-mcp

Discover and register MCP server tools into Hermes toolsets at startup.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill native-mcp-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill native-mcp-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent lacks built-in MCP integration and requires manual boilerplate to connect to MCP servers and expose their tools. This Skill provides a built-in MCP client that auto-discovers tools at startup and injects them into Hermes' toolsets.

Core Features & Use Cases

  • Auto-discovery of MCP tools on startup from configured MCP servers.
  • Supports stdio (command-based) and HTTP MCP transports.
  • Auto-injection of MCP tools into all Hermes platform toolsets for seamless usage.
  • Easy configuration via ~/.hermes/config.yaml under mcp_servers to enable new MCP servers. Use Cases: Connect to an MCP server and immediately access its tools via mcp_server_tool naming.

Quick Start

Configure at least one MCP server in your Hermes config and restart the agent to auto-discover and expose its 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 a Hermes Agent deployment?

This Skill connects to MCP servers defined in the Hermes config and discovers their tools at startup. It automatically registers these external tools and injects them into all Hermes platform toolsets, eliminating the need for manual boilerplate to expose MCP capabilities.

Does MCP integration support both stdio command-based and HTTP transports?

Yes, MCP integration supports both stdio command-based and HTTP transports. You can define either a command or a URL for your MCP server configuration, and the Skill will handle the connection, tool discovery, and registration process seamlessly across both transport types.

How do I configure MCP servers to expose their tools via mcp_server_tool naming?

You configure MCP servers by adding them to the ~/.hermes/config.yaml file under the mcp_servers section. Once configured and the agent is restarted, the tools are auto-discovered and made available using the mcp_server_tool naming convention across all toolsets.

What is the best way to connect external MCP capabilities to Hermes without manual boilerplate?

The best way to connect external MCP capabilities without manual boilerplate is using a built-in MCP client Skill that handles automatic discovery and injection. It connects to your configured MCP servers at startup and exposes their tools as standard tools within the Hermes platform.

Do I need an existing MCP server configuration to use auto-registration for Hermes Agent?

Yes, you need an existing MCP server configuration containing either a command or URL to use auto-registration. The Skill requires this configuration in ~/.hermes/config.yaml to connect, discover tools, and inject them into Hermes toolsets at startup.