native-mcp

Connect MCP servers and auto-discover their tools within Hermes Agent.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/SatangThevalue/ai-skills --skill native-mcp-satangthevalue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/SatangThevalue/ai-skills/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/SatangThevalue/ai-skills --skill native-mcp-satangthevalue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent users often struggle to manually wire integrations to external MCP servers. This Skill enables the agent to connect to MCP servers, auto-discover available tools, and expose them as first-class capabilities without a bridge CLI.

Core Features & Use Cases

  • Auto-discovery and registration of MCP tools on startup
  • Support for stdio and HTTP MCP servers
  • Auto-injection of discovered tools into all Hermes toolsets across platforms
  • Centralized configuration via ~/.hermes/config.yaml

Quick Start

Start the Hermes Agent with MCP enabled to auto-discover and register MCP tools on startup.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I auto-discover and register external MCP tools in Hermes Agent?

To auto-discover MCP tools in Hermes Agent, start the agent with MCP enabled. The capability initializes on startup, connects to configured servers, and injects the discovered tools into all platform toolsets for immediate use without manual wiring.

What is the best way to connect an MCP server without using a bridge CLI?

The best way to connect an MCP server without a bridge CLI is to use the native-mcp capability. It auto-discovers available tools on startup and exposes them as first-class capabilities directly within the Hermes Agent environment.

Does Hermes Agent support both stdio and HTTP transport for MCP server communication?

Yes, Hermes Agent supports both stdio and HTTP transport configurations for MCP server communication. You can configure either transport protocol to enable tool discovery and registration within the platform.

Do I need the Python mcp package to enable MCP tool discovery on startup?

Yes, you need the mcp package for Python to enable MCP tool discovery on startup. Along with the package, you must provide either stdio or HTTP transport configurations to successfully connect and auto-register tools.

How do I configure MCP server connections centrally for auto-injection into toolsets?

You can configure MCP server connections centrally by editing the ~/.hermes/config.yaml file. This centralized configuration allows the Hermes Agent to auto-inject discovered MCP tools into all toolsets across platforms on startup.

Why are my discovered MCP tools not auto-registering in Hermes Agent?

Discovered MCP tools may fail to auto-register if the Python mcp package is missing or if stdio and HTTP transport configurations are invalid. Ensure your ~/.hermes/config.yaml is correctly set up to enable startup initialization and tool discovery.