native-mcp

Discover MCP server tools and register them in Hermes Agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connect Hermes Agent to MCP servers and automatically discover and register their tools for use in conversations.

Core Features & Use Cases

  • Auto-discovery of MCP tools at startup and injection into Hermes tool registries for all platforms.
  • Supports both stdio and HTTP MCP servers, enabling local and remote tool access from any conversation.
  • Consistent tool naming under the mcp_server_tool convention and secure credential handling during tool calls.

Quick Start

Configure your MCP servers in the agent config under mcp_servers and restart Hermes to auto-discover and register their 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 MCP servers to Hermes Agent?

To connect MCP servers to Hermes Agent, configure your servers under the mcp_servers key in ~/.hermes/config.yaml and restart. The Skill auto-discovers and registers their tools at startup using both stdio and HTTP transports.

How does MCP tool discovery work in Hermes?

MCP tool discovery works by reading the mcp_servers configuration at startup, initializing MCP sessions via the mcp package, and injecting discovered tools into all Hermes toolsets. Tools adopt the naming convention mcp_{server}_{tool} for consistent access.

Does Hermes Agent support HTTP MCP servers or only stdio?

Hermes Agent supports both stdio and HTTP MCP servers. This dual transport support enables you to access local tools via stdio and remote tools via HTTP from any conversation across all platforms.

Can I use remote MCP tools in any Hermes conversation?

Yes, you can use remote MCP tools in any Hermes conversation. The startup discovery process injects all registered tools into every Hermes toolset, making both local and remote tools accessible across all platforms.

What is the naming convention for discovered MCP tools in Hermes?

The naming convention for discovered MCP tools is mcp_{server}_{tool}. This standardized format ensures consistent tool identification and secure credential handling when invoking tools across different MCP servers.

Do I need to manually register MCP tools for each Hermes conversation?

No, manual registration is unnecessary. The Skill applies at startup to automatically discover MCP server tools and inject them into all Hermes toolsets, making them available for use in any conversation without per-session setup.