native-mcp

Connects Hermes Agent to external MCP servers via stdio or HTTP and registers their tools with prefixed names.

641|104|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/loongclaw-ai/loongclaw --skill native-mcp-loongclaw-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/loongclaw-ai/loongclaw/tree/main/skills/native-mcp
Command: npx skills add https://github.com/loongclaw-ai/loongclaw --skill native-mcp-loongclaw-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External MCP servers expose powerful tools, but they only become useful when Hermes Agent can discover, secure, and call them as if they were built-in capabilities, which this Skill manages automatically.

Core Features & Use Cases

  • Native MCP integration: on startup, the client connects to each configured MCP server, lists its tools, registers them with the mcp_{server}_{tool} naming convention, and injects them into every Hermes toolset without extra steps.
  • Secure, resilient transport management: supports stdio and HTTP transports with filtered environments, credential redaction, per-call timeouts, and exponential backoff reconnection for reliable long-lived sessions.
  • Sampling, auditing, and tool injection: enables MCP sampling requests, per-server configuration of models and rate limits, and aggregates telemetry so external capabilities behave consistently in all conversations.

Quick Start

Add your MCP servers to the mcp_servers section of ~/.hermes/config.yaml and restart Hermes Agent so their tools appear alongside the built-in capabilities.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I integrate external MCP servers with Hermes Agent?

To integrate external MCP servers with Hermes Agent, add your server configurations to the mcp_servers section of ~/.hermes/config.yaml and restart the agent. This automatically discovers and registers the server tools for direct invocation in conversational workflows.

Does Hermes MCP integration support both stdio and HTTP transport?

Hermes MCP integration supports both stdio and HTTP transports for connecting to external servers. It ensures reliable long-lived sessions through filtered environments, credential redaction, per-call timeouts, and exponential backoff reconnection handling.

How are MCP tools named when registered in Hermes toolsets?

MCP tools are registered using the mcp_{server}_{tool} naming convention. This prefixing system injects the external capabilities into every Hermes toolset automatically on startup, making them available alongside built-in capabilities without extra steps.

Can I configure rate limits and models for individual MCP servers?

You can configure individual MCP servers with specific models and rate limits through per-server configuration. The integration also enables MCP sampling requests and aggregates telemetry so external capabilities behave consistently across all conversations.

Why does my MCP server connection drop during long-lived agent sessions?

MCP server connections may drop during long-lived sessions due to network instability or timeouts. The integration handles this automatically by applying exponential backoff reconnection and per-call timeouts to maintain reliable transport management.