native-mcp

Connect MCP servers and register their tools across stdio and HTTP transports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent needs to connect to MCP servers and access their tools without manual wiring. The native-mcp skill provides automatic discovery and registration of MCP tools, enabling them to be used as Hermes capabilities.

Core Features & Use Cases

  • Auto-discover MCP servers via configured mcp_servers and register their tools with the Hermes tool registry.
  • Support both stdio and HTTP MCP transports, keeping tools accessible across conversations and platforms.
  • Centralize MCP configuration in ~/.hermes/config.yaml and inject MCP tools into all Hermes toolsets for seamless usage.

Quick Start

Configure your mcp_servers in ~/.hermes/config.yaml and restart Hermes 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 connect MCP servers to an agent without manual wiring?

To connect MCP servers without manual wiring, configure them in your YAML settings to enable automatic discovery and tool registration. The system injects them directly into the agent toolset, exposing server tools as native capabilities.

What is the best way to auto-register HTTP and stdio MCP tools?

Auto-registering HTTP and stdio MCP tools is handled natively by a skill supporting both transports. It discovers configured servers at startup and performs idempotent tool registration across all platform toolsets.

How does MCP server discovery work with YAML configuration?

MCP server discovery works by reading the mcp_servers block in your YAML configuration file. Upon startup, the system scans this configuration to find available servers and automatically injects their tools into the agent registry.

Can I use MCP tools across different conversations and platforms?

Yes, you can use MCP tools across different conversations and platforms. The skill injects discovered tools into all platform toolsets, keeping them accessible throughout the agent's lifecycle.

Why are my configured MCP servers not showing up in the tool registry?

If configured MCP servers are not showing up in the tool registry, ensure the YAML configuration is correctly formatted and restart the agent. The discovery process runs at startup and requires a restart to register tools idempotently.

Does native-mcp support both stdio and HTTP transports for MCP servers?

Yes, native-mcp supports both stdio and HTTP transports for MCP servers. It applies automatic discovery and tool registration across both transport types, ensuring comprehensive coverage for server connections.