native-mcp

Connect Hermes Agent to MCP servers and register discovered tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual setup required to connect external MCP servers and make their tools available inside Hermes Agent.

Core Features & Use Cases

  • Automatic MCP server discovery at startup: Reads your MCP server configuration, connects, lists remote tool schemas, and registers them without a separate bridge workflow.
  • First-class tool registration with safe naming: Exposes discovered tools to the agent as mcp_{server_name}_{tool_name} and normalizes names for LLM compatibility.
  • Transport support for stdio and HTTP: Runs local stdio-based MCP servers (e.g., via npx/uvx) or connects to remote HTTP/StreamableHTTP MCP endpoints.
  • Security-minded execution: Filters inherited environment variables for stdio subprocesses and redacts credential-like values from tool errors to reduce leakage risk.
  • Optional server-side LLM sampling: Supports MCP sampling/createMessage so MCP servers can request model completions during tool execution.

Quick Start

Configure your MCP servers in ~/.hermes/config.yaml under mcp_servers, then restart Hermes Agent so it connects, discovers tools, and registers them as mcp_{server}_{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 an MCP server to my agent and discover its tools?

MCP server tool discovery is handled automatically by reading your MCP server configuration at agent startup, connecting to the server, listing remote tool schemas, and registering them as callable first-class tools. You only need to configure your servers in the Hermes config file and restart the agent.

Can I use both stdio and HTTP transports for MCP tool integration?

MCP tool integration supports both local stdio-based subprocess transports via npx/uvx and remote HTTP/StreamableHTTP MCP endpoints for tool discovery, registration, and execution across startup workflows and recurring sessions.

How does the agent handle environment variables and credentials when running stdio MCP servers?

Environment variables are filtered for stdio subprocesses to reduce leakage risk, and credential-like values are redacted from tool errors, ensuring secure execution when connecting to MCP servers.

What naming convention is used when registering discovered MCP tools?

Discovered MCP tools are exposed to the agent using the normalized naming convention mcp_{server_name}_{tool_name}, ensuring LLM compatibility and deterministic tool calling across all platforms.

Do I need a separate bridge workflow to make MCP tools available to the agent?

No separate bridge workflow is required. The native MCP integration eliminates manual setup by automatically connecting to MCP servers, discovering available tools, and registering them directly within the Hermes Agent environment.

Can MCP servers request model completions during tool execution?

Yes, MCP servers can request model completions during tool execution through optional server-side LLM sampling support using the MCP sampling/createMessage protocol.