skills.rest
jaredcroxton
jaredcroxtonCOMMUNITY
Explore all skills by this author →
GitHub

native-mcp

Register MCP server tools into Hermes via startup discovery.

Updated May 16, 2026
Search Tags:#automation#mcp#tool discovery#stdio#tool registration#http integration#enterprise integrations
One-click install
npx skills add https://github.com/jaredcroxton/hermes-mirror --skill native-mcp-jaredcroxton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/jaredcroxton/hermes-mirror/tree/main/agents/skills/mcp/native-mcp
Command: npx skills add https://github.com/jaredcroxton/hermes-mirror --skill native-mcp-jaredcroxton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Native MCP tool discovery lets you connect external MCP servers and use their tools directly inside Hermes without running a separate bridge workflow.

Core Features & Use Cases

  • Auto-discovers MCP tools at startup and registers them in Hermes as first-class tools.
  • Supports stdio and HTTP MCP transports so you can integrate local command-based servers and remote HTTP servers.
  • Applies safe credential handling by filtering subprocess environment variables and redacting credential-like strings in errors.

Quick Start

Add your MCP servers under the mcp_servers key in ~/.hermes/config.yaml, restart Hermes, and then call a tool like mcp_<server_name>_<tool_name>.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I register MCP server tools in Hermes without using a bridge?▼

Hermes natively connects to MCP servers by reading configuration from ~/.hermes/config.yaml, performing startup discovery, and injecting tools directly into the platform without requiring a separate bridge workflow.

Does Hermes MCP integration support both stdio and HTTP transports?▼

Yes, Hermes MCP integration supports both local stdio servers configured via command and arguments, and remote HTTP servers configured via URL and headers, enabling broad tool connectivity.

How are MCP tool names formatted when registered in Hermes?▼

Registered MCP tools are named using the mcp_{server}_{tool} pattern with normalized identifiers. You invoke them directly in Hermes using this naming convention after startup discovery.

How does MCP tool discovery handle credentials and subprocess environment variables?▼

MCP tool discovery applies safe credential handling by filtering subprocess environment variables and redacting credential-like strings in error messages to protect sensitive data during connections.

What do I need to configure before connecting external MCP servers to Hermes?▼

You must define your MCP servers under the mcp_servers key in ~/.hermes/config.yaml, then restart Hermes. The platform connects with timeouts and retries to expose the tools.

Can I enable MCP sampling when integrating remote HTTP servers?▼

Yes, MCP sampling can optionally be enabled when integrating remote HTTP servers. This feature is supported alongside standard tool registration for both local stdio and remote HTTP transports.

Related Skills

Explore More Software Engineering Skills→
MarbleSodasMarbleSodas

native-mcp

Discover and register MCP tools from stdio or HTTP servers into Hermes Agent.

Community
Intermediate
GregsGreyCodeGregsGreyCode
6

native-mcp

Connects Hermes Agent to MCP servers and auto-discovers tools for injection into tool sets.

Community
Intermediate
danmartinez78danmartinez78

native-mcp

Connect Hermes Agent to MCP servers and register discovered tools.

Community
Intermediate
tambo-aitambo-ai
11.2k

tools-and-context

Register custom tools, connect MCP servers, and manage dynamic context in Tambo.

Official
Intermediate