skills.rest
MarbleSodas
MarbleSodasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

native-mcp

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

Updated Apr 9, 2026
Search Tags:#tool integration#mcp#auto-discovery#local-first#stdio transport#agent tooling#http mcp
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill native-mcp-marblesodas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill native-mcp-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual setup work of connecting MCP servers and wiring their tools into Hermes Agent, so external capabilities can be used instantly in conversations.

Core Features & Use Cases

  • Connects to MCP servers and discovers tools at startup: Automatically reads your configured mcp_servers, establishes transport connections, and lists available tools.
  • Registers MCP tools as first-class Hermes tools: Exposes discovered tools alongside built-ins and prefixes them using the mcp_{server}_{tool} naming convention.
  • Supports stdio and HTTP/StreamableHTTP transports: Runs local command-based MCP servers (via npx/uvx) and connects to remote HTTP MCP servers.

Use Case: You want a Hermes-powered assistant to access GitHub and a local filesystem without custom glue code; configure both MCP servers and then ask the agent to list issues or read files directly.

Quick Start

Configure your MCP servers in ~/.hermes/config.yaml under the mcp_servers key, restart Hermes Agent, and then ask the agent to call an MCP-provided tool by natural language.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I auto-discover MCP tools for my agent?▼

Auto-discover MCP tools by configuring servers in ~/.hermes/config.yaml; the agent connects via stdio or HTTP at startup, lists available tools, and injects them into all platform toolsets automatically.

How do I connect local and remote MCP servers to Hermes Agent?▼

Connect MCP servers by defining them under the mcp_servers key in config.yaml; use command, args, and env for stdio servers, or url and headers for remote HTTP/StreamableHTTP transports.

Do I need the Python mcp SDK to use MCP servers with Hermes?▼

The optional Python mcp SDK is required for client support when connecting to certain MCP servers, while transport-specific settings like command, args, url, and headers handle the actual connections.

How are discovered MCP tools named when registered in Hermes?▼

Discovered MCP tools are named using the mcp_{server_name}_{tool_name} convention, exposing them as first-class tools alongside built-ins for direct invocation via natural language requests.

What are the limitations of auto-discovering MCP tools at startup?▼

Limitations include requiring a configured mcp_servers section for idempotent startup discovery, enforcing safe environment filtering, and applying configurable timeouts during stdio or HTTP transport connections.

Related Skills

Explore More Software Engineering Skills→
jaredcroxtonjaredcroxton

native-mcp

Register MCP server tools into Hermes via startup discovery.

Community
Intermediate
zengbaochengzengbaocheng

native-mcp

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

Community
Intermediate
jleechanorgjleechanorg

native-mcp

Discover and register MCP server tools into Hermes Agent toolsets.

Official
Advanced
eastreamseastreams
641

native-mcp

Connect to external MCP servers and expose their tools as native Hermes Agent capabilities.

Official
Advanced