native-mcp

Connects Hermes Agent to MCP servers and auto-registers their tools.

97|8|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/peteromallet/megaplan --skill native-mcp-peteromallet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/peteromallet/megaplan/tree/main/megaplan/agent/skills/mcp/native-mcp
Command: npx skills add https://github.com/peteromallet/megaplan --skill native-mcp-peteromallet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent needs a reliable way to connect to MCP servers, discover their tools, and register them as native tools. This skill provides a built-in MCP client to automate that workflow.

Core Features & Use Cases

  • Auto-discovery of MCP tools on startup and on-demand when servers join.
  • Supports stdio and HTTP transports with automatic reconnection and secure filtering.
  • Zero-config tool injection into Hermes Agent toolsets for immediate accessibility.

Quick Start

Configure Hermes Agent to connect to your MCP server(s) and restart the agent to automatically discover and register available tools.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I connect Hermes Agent to MCP servers?

To connect Hermes Agent to MCP servers, configure the connection settings and restart the agent. The native MCP client automatically establishes connections over stdio or HTTP transports and registers available tools.

What is automatic MCP tool discovery and how does it work?

Automatic MCP tool discovery is the process of identifying and registering external tools from MCP servers as native Hermes tools. It runs on startup and on-demand when new servers join, applying security filtering before zero-config tool injection into Hermes toolsets.

Can I use stdio and HTTP transports to integrate external MCP servers?

Yes, you can use both stdio and HTTP transports to integrate external MCP servers. The skill supports both transport protocols with automatic reconnection to ensure persistent background connections and reliable tool accessibility.

How are MCP tools named when injected into Hermes Agent toolsets?

MCP tools are named using the mcp_{server}_{tool} naming convention when injected into Hermes Agent toolsets. This ensures clear identification and immediate accessibility across all native toolsets without manual configuration.

Do I need to manually configure tools discovered from MCP servers?

No, you do not need to manually configure tools discovered from MCP servers. The skill provides zero-config tool injection, automatically applying security filtering and registering all discovered tools directly into all Hermes toolsets.