skills.rest
rnben
rnbenCOMMUNITY
Explore all skills by this author →
GitHub

native-mcp

Connect Hermes Agent to MCP servers and register discovered tools.

1|Updated Apr 18, 2026
Search Tags:#automation#mcp#http#stdio#tool-discovery#external-tools#hermes-agent
One-click install
npx skills add https://github.com/rnben/hermes-skills --skill native-mcp-rnben
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/rnben/hermes-skills/tree/main/plugins/mcp-skills/skills/native-mcp
Command: npx skills add https://github.com/rnben/hermes-skills --skill native-mcp-rnben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent commonly requires manual setup to integrate external MCP servers. This skill provides a built-in MCP client that connects to MCP servers, discovers their tools, and registers them as native Hermes Agent tools, enabling direct access to external capabilities.

Core Features & Use Cases

  • Auto-discovery of MCP tools on startup and automatic registration under the mcp_{server}_{tool} naming scheme
  • Supports stdio and HTTP transports with automatic reconnection and security filtering
  • Zero-config tool injection across all Hermes toolsets, with local and remote MCP servers
  • Real-world use: connect to an MCP server exposing filesystem or GitHub tools and use them from Hermes across channels

Quick Start

Install and configure an MCP server, then restart Hermes Agent to enable auto-discovery and tool injection.

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 external MCP tools in Hermes Agent?▼

To auto-discover MCP tools, connect Hermes Agent to MCP servers using this skill, which automatically registers exposed tools as native Hermes tools under the mcp_{server}_{tool} naming scheme on startup.

Can I connect Hermes to remote MCP servers over HTTP?▼

Yes, Hermes Agent supports connecting to remote MCP servers over HTTP transports, alongside local stdio transports, with automatic reconnection and security filtering for external tool integration.

Why are my newly configured MCP tools not showing up in Hermes toolsets?▼

Newly configured MCP tools require a Hermes Agent restart to trigger the auto-discovery process, which connects to the MCP servers defined in ~/.hermes/config.yaml and injects the tools into all toolsets.

What's the best way to integrate external filesystem or GitHub tools into Hermes?▼

The best way is connecting Hermes to an MCP server exposing those tools, allowing the agent to auto-discover and register them as native tools, enabling direct access across all channels.

Does auto-registering external MCP tools require manual configuration for each tool?▼

No, auto-registering MCP tools requires zero manual tool configuration. You only need to define the MCP servers in config.yaml, and the skill handles tool discovery and native registration automatically on startup.

Related Skills

Explore More Software Engineering Skills→
cloudlinesscloudliness

native-mcp

Connect to MCP servers and register discovered tools as Hermes-native tools.

Community
Advanced
GregsGreyCodeGregsGreyCode
6

native-mcp

Connects Hermes Agent to MCP servers and auto-discovers tools for injection into tool sets.

Community
Intermediate
fikriaffikriaf

native-mcp

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

Community
Advanced
GitnappGitnapp

native-mcp

Connect AI agents to external Model Context Protocol servers and register their tools.

Community
Advanced