native-mcp

Connects MCP servers and registers their tools for use in JARVIS.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill native-mcp-sethypagna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native-mcp
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/mcp/native-mcp
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill native-mcp-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually bridging external MCP servers into JARVIS by making their tools available as native, first-class agent capabilities at startup.

Core Features & Use Cases

  • Automatic tool discovery: Connects to configured MCP servers, discovers their tools, and registers them for use alongside built-in JARVIS tools.
  • Flexible transports: Supports both local stdio servers for command-based integrations and remote HTTP servers for shared or hosted MCP endpoints.
  • Operational safety: Filters inherited environment variables, redacts credential-like values from errors, and keeps connections persistent with retry handling.
  • Use cases: Connect filesystem, GitHub, database, or internal API servers so the agent can call those tools in any conversation without extra setup.

Quick Start

Add one or more servers to your JARVIS MCP configuration, restart the app, and then ask JARVIS to use the newly discovered tools.

Frequently Asked Questions about native-mcp

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

FAQPage Schema
How do I connect MCP servers to JARVIS for direct tool use?

To connect MCP servers to JARVIS, add your server configurations to the mcp_servers config file and restart the application. The Skill automatically discovers and registers the available tools for use in conversations.

Does the JARVIS MCP integration support both local stdio and remote HTTP servers?

Yes, the JARVIS MCP integration supports both local stdio servers for command-based integrations and remote HTTP servers for shared or hosted endpoints, making external tools available as native agent capabilities.

What tools can I use through MCP server discovery in JARVIS?

Through MCP server discovery in JARVIS, you can use filesystem, GitHub, database, or internal API tools. The agent calls these registered tools directly in any conversation without requiring extra manual setup.

How are credentials handled when registering remote MCP tools in JARVIS?

When registering remote MCP tools in JARVIS, the Skill filters inherited environment variables for operational safety and redacts credential-like values from error messages to protect sensitive data during connections.

Do I need the Python mcp package to enable tool discovery in JARVIS?

Yes, you need the optional Python mcp package to enable tool discovery in JARVIS. A valid mcp_servers configuration is also required to establish persistent background connections with retry handling.

Why are my discovered MCP tools not showing up after restarting JARVIS?

Discovered MCP tools may not show up in JARVIS if the mcp_servers configuration is invalid or the optional Python mcp package is missing. Verify your setup and ensure safe environment filtering is applied.