native-mcp

Integrate external MCP servers into Hermes Agent via stdio or HTTP.

Updated May 10, 2026
One-click install
npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill native-mcp-mateus2411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/Mateus2411/Hermes-PersonalBot/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill native-mcp-mateus2411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp, and includes references (resource) components.

What problem does it solve?

It solves the problem of manually wiring external tool servers into Hermes Agent by automatically connecting to MCP servers and registering their tools for immediate use.

Core Features & Use Cases

  • Automatic tool discovery at startup: Hermes connects to configured MCP servers, calls list_tools(), and registers returned tools into the agent’s tool registry.
  • Multiple transports (stdio and HTTP): Supports local stdio MCP servers launched via command/args and remote MCP servers via URL (including optional HTTP headers).
  • Collision-free tool naming: Exposes tools with the naming pattern mcp_{server_name}_{tool_name} (hyphens/dots normalized) so multiple servers can coexist safely.
  • Production-minded operations: Persistent background connections, reconnection with exponential backoff, per-tool-call timeouts, and optional sampling support for server-initiated LLM requests.

Quick Start

Add your MCP server(s) to ~/.hermes/config.yaml under mcp_servers, restart Hermes Agent, and then ask it to call a discovered MCP tool like “get the current time using the MCP time tool.”

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I connect MCP servers to my agent for tool discovery?

To connect MCP servers for tool discovery, you configure server definitions in ~/.hermes/config.yaml. The agent reads this configuration at startup, automatically connects to the MCP servers, and registers their tools for immediate invocation.

How do I configure remote HTTP MCP servers with authentication headers?

You can configure remote HTTP MCP servers by adding their URL and optional HTTP headers to ~/.hermes/config.yaml. The agent uses these headers to authenticate and establish persistent background connections to the remote endpoints.

How does stdio MCP server integration work for local command execution?

Stdio MCP server integration works by launching local servers through specified command and args in your configuration file. The agent communicates with these background processes over standard input and output to discover and invoke their registered tools.

Can I run multiple MCP servers without tool name collisions?

You can safely run multiple MCP servers without name collisions because the system registers tools using a normalized naming pattern. Each tool is exposed as mcp_{server_name}_{tool_name}, ensuring unique identification across all connected servers.

What happens when an MCP server connection drops during an agent session?

When an MCP server connection drops during a session, the system automatically attempts reconnection using an exponential backoff strategy. It also applies per-tool-call timeouts to prevent agent hangs while waiting for unresponsive servers.

Does MCP integration support server-initiated LLM sampling requests?

MCP integration optionally supports server-initiated LLM sampling requests. You can enable this feature to allow connected MCP servers to leverage the agent's language model capabilities for their internal processing requirements.