native-mcp

Connects external MCP servers and registers their tools in Hermes Agent via stdio, HTTP, or StreamableHTTP endpoints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of wiring external MCP servers into Hermes Agent by letting the agent discover, register, and use their tools automatically at startup.

Core Features & Use Cases

  • Automatic Tool Discovery: Connects to configured MCP servers and registers their available tools as native agent tools.
  • Flexible Transports: Supports local stdio servers and remote HTTP or StreamableHTTP servers for broad integration coverage.
  • Operational Safety: Filters inherited environment variables, redacts sensitive tokens in errors, and retries dropped connections with backoff.
  • Use Case: Use it to add filesystem access, GitHub actions, database queries, or internal API tools to every Hermes conversation without a bridge CLI.

Quick Start

Add one MCP server to your Hermes configuration and restart the agent so it can discover and expose the server’s tools automatically.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I expose external MCP server tools to an agent automatically?

To connect MCP servers to Hermes Agent, add your server configurations and restart the agent. The Skill discovers the servers at startup, automatically registering their available tools for immediate use in conversations.

Can I use remote HTTP endpoints with local stdio MCP servers?

Yes, you can connect both local stdio MCP servers and remote HTTP or StreamableHTTP endpoints. This dual transport support enables broad integration coverage for filesystem, GitHub, database, and API workflows.

Do I need the mcp Python package to connect MCP servers?

Yes, the mcp Python package is required to connect MCP servers and register their tools. The Skill relies on this dependency to handle underlying protocol communication and tool discovery.

What's the best way to secure environment variables when connecting MCP servers?

To secure environment variables when integrating MCP servers, the Skill filters inherited environment variables and redacts sensitive tokens in error logs. It also applies reconnection retries with backoff for dropped connections.

Why does my MCP server tool discovery fail after restarting the agent?

MCP server tool discovery might fail if persistent startup discovery is interrupted or the required mcp Python package is missing. The Skill needs valid per-server configurations to successfully connect and register tools.