native-mcp

Connect to MCP servers at startup to discover and register their tools.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill native-mcp-chris-chai-minjae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill native-mcp-chris-chai-minjae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent needs a way to connect to external MCP servers, discover their tools, and register them as native Hermes tools to avoid manual integration and to broaden capabilities.

Core Features & Use Cases

  • Built-in MCP client that discovers MCP tools at startup and registers them in Hermes' tool registry.
  • Automatic tool registration with consistent naming across servers (mcp_{server}_{tool}).
  • Supports stdio and HTTP transports with automatic reconnects, security filtering, and zero-config tool injection.
  • Use cases include adding external capabilities (filesystem, APIs, CI tools) via MCP and enabling cross-server tool availability in all conversations.

Quick Start

Configure MCP servers in your ~/.hermes/config.yaml under mcp_servers and restart Hermes Agent to begin tool discovery.

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?

To auto-discover MCP server tools, configure your MCP servers in the ~/.hermes/config.yaml file under mcp_servers and restart Hermes Agent. The built-in client connects at startup to register tools automatically using the mcp_{server}_{tool} naming convention.

What transports are supported for connecting to MCP servers?

MCP server connections support both stdio and HTTP transports. The integration includes automatic reconnects to maintain persistent tool availability and ensure reliable cross-server communication across all platforms without manual intervention.

Does MCP tool integration require manual configuration for each tool?

No, MCP tool integration uses zero-config tool injection. Once servers are specified in the Hermes config, security filtering and autonomous tool discovery handle the registration, eliminating the need for manual tool integration.

Can I add external filesystem and API capabilities to Hermes Agent via MCP?

Yes, you can add external capabilities such as filesystem access, APIs, and CI tools via MCP servers. This enables cross-server tool availability, broadening Hermes Agent's capabilities in all conversations without manual integration.

How does security filtering work for auto-registered MCP tools?

Security filtering is enforced during the zero-config tool injection process. It evaluates discovered MCP tools at startup to ensure only authorized and safe tools are registered as native Hermes Agent tools in the tool registry.