hermes-mcp-add

Connects remote HTTP MCP servers to self-hosted Hermes agents over SSH.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the trial-and-error of connecting an arbitrary remote HTTP MCP server to a self-hosted Hermes agent, especially when the auth format is undocumented or inconsistent.

Core Features & Use Cases

  • Auth Discovery: Probes multiple credential shapes to determine whether the server expects a bearer token, custom header, path token, or query token.
  • Safe Secret Handling: Stores the token in the Hermes runtime environment file with restrictive permissions instead of exposing it in config blocks or chat logs.
  • Reliable Registration: Registers the MCP server, reloads the gateway correctly, and verifies that Hermes can actually use the tools.
  • Use Case: A user has a new vendor MCP endpoint with unclear documentation and needs to connect it to Hermes without breaking existing setup or leaking secrets.

Quick Start

Use the hermes-mcp-add skill to connect a remote HTTP MCP server to your self-hosted Hermes agent by discovering the correct auth method, storing the secret securely, registering the server, and verifying that the gateway can reach it.

Frequently Asked Questions about hermes-mcp-add

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

FAQPage Schema
How do I connect a remote HTTP MCP server to a self-hosted Hermes agent?

Connecting a remote HTTP MCP server to Hermes involves probing multiple authentication variants, storing the discovered token in the environment file, registering the server, reloading the gateway, and verifying authenticated tools/list access.

How does auth discovery work for an MCP server with undocumented token formats?

Auth discovery probes multiple credential shapes to determine whether the MCP server expects a bearer token, custom header, path token, or query token, eliminating trial-and-error when documentation is unclear or inconsistent.

What is the safest way to store MCP server tokens for Hermes integrations?

The safest way to store MCP server tokens is writing them to the Hermes runtime environment file with restrictive permissions, preventing exposure in config blocks or chat logs.

Can I integrate an MCP server into Hermes over SSH without breaking existing setup?

Yes, you can integrate an MCP server over SSH without breaking existing setup by applying safe secret handling and reliable registration, which reloads the gateway correctly and verifies access.

What should I do if my Hermes gateway cannot reach the newly registered MCP server?

If the gateway cannot reach the MCP server, verify the auth discovery completed successfully, confirm the token is in the environment file, and ensure the gateway was reloaded correctly before checking tools/list access.