native-mcp

Connect to MCP servers and auto-register their tools in Argo Agent.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nadicodeai/argo-agent --skill native-mcp-nadicodeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/nadicodeai/argo-agent/tree/main/skills/mcp/native-mcp
Command: npx skills add https://github.com/nadicodeai/argo-agent --skill native-mcp-nadicodeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP client: connect servers, discover their tools, and expose them as first-class capabilities inside Argo Agent.

Core Features & Use Cases

  • Auto-discovery of MCP servers at startup and automatic registration of their tools.
  • Support for stdio and HTTP MCP transports, with tools injected into all Argo toolsets.
  • Use cases include integrating external capabilities from MCP servers and extending Argo Agent functionality in workflows.

Quick Start

Configure your MCP servers in ~/.argo/config.yaml under mcp_servers and restart the Argo Agent to auto-discover and register MCP tools.

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 and register MCP server tools in Argo Agent?

To auto-discover MCP server tools, configure your MCP servers in the ~/.argo/config.yaml file under the mcp_servers key and restart Argo Agent to trigger startup-time discovery and automatic tool registration.

What is MCP tool auto-discovery and how does it work?

MCP tool auto-discovery is a startup-time process that connects to configured stdio and HTTP MCP servers, identifies their available tools, and auto-injects them as first-class capabilities into all argo-* toolsets.

Do I need the mcp Python package to connect MCP servers to Argo?

Yes, you need the mcp Python package installed in your environment, along with a valid ~/.argo/config.yaml mcp_servers configuration, to enable automatic MCP server discovery and tool generation.

Can I use both stdio and HTTP MCP transports with Argo Agent?

Yes, Argo Agent supports both stdio and HTTP MCP transports, allowing you to connect to diverse MCP servers and seamlessly inject their discovered tools into all conversations and workflows.

Why are my configured MCP tools not showing up in Argo workflows?

Your MCP tools may not show up if the ~/.argo/config.yaml mcp_servers configuration is invalid, the mcp Python package is missing, or the Argo Agent was not restarted to trigger startup-time discovery.