hermes-native-mcp

Configures Hermes Agent's MCP client for HTTP and stdio servers with TLS trust handling.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure and use Hermes Agent's built-in MCP client to connect to stdio and HTTP MCP servers, including testing, troubleshooting, and TLS trust fixes for internal HTTPS endpoints.

Core Features & Use Cases

  • Configure per-server MCP endpoints (HTTP or stdio) in Hermes.
  • Discover and verify MCP tools, troubleshoot TLS trust issues, and ensure tools appear as mcp_<server>_<tool> names.
  • Use cases include adding new MCP servers, validating tool availability, and resolving certificate trust problems in internal networks.

Quick Start

Ask Hermes to connect to your MCP server and verify the available tools.

Frequently Asked Questions about hermes-native-mcp

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

FAQPage Schema
How do I configure an MCP client to connect to HTTP and stdio servers?

To configure an MCP client, you set per-server endpoint options for HTTP or stdio servers within your agent. This connects the client to the servers and exposes their tools using the mcp_<server>_<tool> naming convention.

Why does my MCP client fail to connect to internal HTTPS endpoints?

Internal HTTPS endpoints fail when TLS trust is misconfigured. You need to apply TLS trust fixes specific to your internal network to ensure secure connections resolve correctly during server discovery.

How are MCP tools named and discovered after connecting a server?

MCP tools are discovered and named using the mcp_<server>_<tool> format. After configuring your endpoint, you can verify availability through a guided discovery process to ensure the tools appear correctly.

Can I troubleshoot MCP server discovery and tool availability issues?

Yes, you can troubleshoot MCP server discovery by following guided verification steps. This process tests endpoint connectivity and validates that the expected tools appear as mcp_<server>_<tool> names.

Does this MCP configuration support both local and remote network endpoints?

Yes, the configuration supports both local and remote network endpoints. It applies per-server options to stdio and HTTP MCP servers, ensuring secure tool management across different network environments.