native-mcp

Connect Hermes Agent to MCP servers and register discovered tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Agent needs a built-in MCP client to connect to MCP servers at startup, automatically discovering tools and registering them as native Hermes tools, without requiring a bridge CLI.

Core Features & Use Cases

  • Auto-discovery of MCP servers and automatic injection of discovered tools into all Hermes toolsets.
  • Supports stdio and HTTP transports with automatic reconnection, and security filtering to protect credentials.
  • Zero-config tool exposure across conversations, enabling immediate use of MCP-provided tools.

Quick Start

Configure your MCP server connections in the Hermes Agent config and restart the agent 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 automatically discover and register MCP server tools in Hermes Agent?

To automatically discover and register MCP server tools, configure your MCP server connections in the Hermes Agent config and restart the agent. This triggers auto-discovery, injecting discovered tools into all Hermes toolsets without requiring a bridge CLI.

Does Hermes Agent MCP client support stdio and HTTP transports?

Yes, the native MCP client supports both stdio and HTTP transports for connecting to external MCP servers. It also includes automatic reconnection capabilities to maintain persistent tool access across conversations.

What is the best way to expose MCP tools natively without a bridge CLI?

The best way to expose MCP tools natively is using the built-in MCP client to connect at startup. This directly registers discovered tools as native Hermes tools, enabling zero-config tool exposure without needing a bridge CLI.

Can I filter credentials and protect sensitive data when connecting to MCP servers?

Yes, you can protect sensitive data when connecting to MCP servers. The native MCP client includes security filtering specifically designed to protect credentials during tool discovery and registration operations.

Why do I need to configure mcp_servers for Hermes Agent tool discovery?

You need to configure mcp_servers to define external server connections. This configuration satisfies the requirement for automatic MCP tool discovery, enabling universal injection of those tools into every Hermes platform toolset.