native-mcp

Connect MCP servers and register external tools for agent use.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Native MCP Client removes the manual setup needed to expose external MCP server capabilities inside Hermes Agent, so connected tools are discovered and ready to use automatically.

Core Features & Use Cases

  • Startup Discovery: Connects to configured MCP servers on launch and registers their tools with Hermes.
  • Multiple Transports: Supports local stdio servers and remote HTTP or StreamableHTTP endpoints.
  • Operational Safety: Filters environment variables, redacts credential-like errors, and retries dropped connections.
  • Use Case: Use it to add filesystem access, GitHub actions, database tools, or API integrations to every conversation without a bridge CLI.

Quick Start

Add your MCP server configuration to Hermes Agent and restart it so the native client can discover and register 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 connect external MCP servers to my agent?

To connect external MCP servers to your agent, add your server configuration to Hermes Agent and restart. The native client automatically discovers and registers the server's tools without requiring a bridge CLI.

What is auto discovery for MCP tools?

Auto discovery for MCP tools is a startup process where the client connects to configured MCP servers on launch and automatically registers their external capabilities, such as filesystem access or database tools, for agent use.

Does MCP integration support both local stdio and remote HTTP endpoints?

Yes, MCP integration supports multiple transports. It connects to local stdio servers and remote HTTP or StreamableHTTP endpoints to register external tools for agent workflows.

How are credentials handled during MCP server connections?

Credentials are handled with operational safety by filtering environment variables and redacting credential-like errors during connection and execution, while also retrying dropped connections automatically.

What can I do with auto-registered MCP tools?

With auto-registered MCP tools you can add filesystem access, GitHub actions, database tools, or API integrations to every conversation without manual setup or a bridge CLI.