native-mcp

Name: native-mcp
Availability: InStock
Author: garrettroi

Connect to MCP servers and register their tools in Hermes Agent.

Updated Mar 12, 2026

Search Tags:#automation #protocol #mcp #external services #tools #integrations

Ready to run

npx skills add https://github.com/GarrettRoi/open-manus --skill native-mcp-garrettroi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/GarrettRoi/open-manus/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/GarrettRoi/open-manus --skill native-mcp-garrettroi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between external Model Context Protocol (MCP) servers and the Hermes Agent, allowing you to leverage a vast ecosystem of tools directly within your agent's workflow without complex setup.

Core Features & Use Cases

Seamless Tool Discovery: Automatically discovers and registers tools from connected MCP servers.
Broad Transport Support: Connects via both standard input/output (stdio) and HTTP transports.
Automatic Reconnection & Security: Handles disconnections with automatic retries and filters sensitive information.
Use Case: Imagine you have an MCP server providing access to a company database. This Skill connects to it, registers the database tools (e.g., mcp_db_query), and allows you to query the database directly from Hermes Agent in any conversation.

Quick Start

Configure your MCP servers in ~/.hermes/config.yaml under the mcp_servers key and restart Hermes Agent.

Frequently Asked Questions about native-mcp

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

FAQPage Schema

How do I integrate external MCP servers with my agent workflow?▼

Integrating external MCP servers involves connecting via stdio or HTTP transports, allowing the agent to automatically discover and register external tools natively without complex setup.

What transports are supported for connecting to Model Context Protocol servers?▼

Both standard input/output (stdio) and HTTP transports are supported for connecting to Model Context Protocol servers, ensuring broad compatibility with various external service architectures.

How does the agent handle MCP server disconnections during a session?▼

MCP server disconnections are handled with automatic reconnection retries, ensuring persistent access to registered tools and maintaining workflow continuity during transient network failures.

Can I filter sensitive information when registering external tools via MCP?▼

Security filtering is applied during tool registration via MCP, automatically screening out sensitive information from discovered tools before injecting them into the agent's capabilities.

Do I need manual configuration to inject MCP tools into the agent?▼

Zero-configuration tool injection is supported, meaning no manual setup is needed to register tools; the agent automatically discovers and registers them from connected MCP servers.