native-mcp

Connects MCP servers via stdio or HTTP and registers their tools for agent use.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill native-mcp-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/CHENHUI-X/toolbox/tree/main/custom-skills/mcp/native-mcp
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill native-mcp-chenhui-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp.

What problem does it solve? Integrating external tools and services into an AI agent normally requires custom bridge code or manual CLI calls. This Skill lets you connect MCP servers directly to Hermes Agent so their tools are auto-discovered and callable in every conversation. ## Core Features & Use Cases - Automatic Tool Discovery: On startup, the agent connects to configured MCP servers, lists their tools, and registers them with a mcp_{server}_{tool} naming prefix. - Dual Transport Support: Run local stdio servers via npx or uvx commands, or connect to remote servers over HTTP/StreamableHTTP with custom headers. - Security Controls: Subprocess environments are filtered to safe baseline variables, and credential-like patterns are redacted from error messages shown to the LLM. - Use Case: Add a GitHub MCP server with a personal access token in ~/.hermes/config.yaml, restart the agent, and immediately ask it to list issues or create pull requests using the auto-registered mcp_github_* tools. ## Quick Start Add an MCP server entry under the mcp_servers key in ~/.hermes/config.yaml and restart the agent to make its tools available.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I connect an MCP server to Hermes Agent?

Add an entry under the mcp_servers key in ~/.hermes/config.yaml with either a command and args for stdio servers or a url for HTTP servers, then restart the agent. Tools are discovered at startup and registered with the mcp_{server}_{tool} prefix.

What is the difference between native MCP and mcporter?

The native MCP client connects servers at startup and keeps persistent connections with tools available in every conversation. mcporter is for ad-hoc, one-off MCP tool calls from the terminal without any configuration.

Does the MCP client support remote HTTP servers?

Yes, HTTP and StreamableHTTP transports are supported by setting a url and optional headers in the server config. Your installed mcp package must include mcp.client.streamable_http, otherwise upgrade it with pip install --upgrade mcp.

Why are my MCP tools not appearing after configuration?

Check that servers are listed under the mcp_servers key with correct YAML indentation, that the mcp package is installed, and that the command binary like npx or uvx is on PATH. Registered tools use the mcp_{server}_{tool} naming pattern.

Are my API keys safe when running stdio MCP servers?

Subprocesses receive only a filtered baseline environment such as PATH and HOME, not your full shell environment. Secrets must be explicitly passed via the env config key, and credential patterns are redacted from error messages shown to the LLM.