native-mcp

Connect MCP servers over stdio or HTTP and register their tools as Hermes Agent tools.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill native-mcp-hugoalmeidamoreira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/HugoAlmeidaMoreira/zeus-agent/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill native-mcp-hugoalmeidamoreira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent often needs to access tools provided by external MCP servers. This skill solves the problem of manual setup by enabling automatic connection to MCP servers and exposing their tools (stdio/HTTP) as native tools in all conversations.

Core Features & Use Cases

  • Auto-discovers MCP tools on startup from configured mcp_servers and registers them in Hermes tool registry.
  • Injects MCP tools into all Hermes platform toolsets for immediate availability.
  • Supports both stdio and HTTP MCP transports with configurable timeouts and basic security handling.

Quick Start

Configure mcp_servers in your Hermes config and start Hermes Agent to automatically discover and register MCP tools.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I automatically register MCP server tools in Hermes Agent?

To automatically register MCP server tools, configure mcp_servers in your Hermes config; on startup, the agent discovers and injects these tools into all Hermes platform toolsets for immediate use.

What transports can I use to connect MCP servers to Hermes?

You can connect MCP servers using either stdio or HTTP transports, with configurable timeouts and basic security handling to manage tool discovery and registration.

Do I need to manually inject MCP tools into each Hermes conversation?

No, you do not need to manually inject MCP tools; startup-wide discovery automatically registers configured MCP tools and injects them into all Hermes platform toolsets natively.

What is the process for discovering external MCP tools on startup?

MCP tool discovery on startup involves scanning configured mcp_servers, establishing a stdio or HTTP connection, and registering the discovered tools directly into the Hermes tool registry.

Can I configure timeouts and security for MCP server connections?

Yes, you can manage MCP server connections with configurable timeouts and basic security considerations to ensure safe and reliable tool registration across stdio and HTTP transports.