add-mcp-tool

Add MCP tools to the nucleo server with CLI wrapping and cargo check validation.

2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mateonunez/nucleo --skill add-mcp-tool-mateonunez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-mcp-tool
Source: https://github.com/mateonunez/nucleo/tree/main/.claude/skills/add-mcp-tool
Command: npx skills add https://github.com/mateonunez/nucleo --skill add-mcp-tool-mateonunez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to add new MCP tools to the nucleo server, enabling Claude Desktop integration and tool orchestration.

Core Features & Use Cases

  • Tool scaffolding: define a tool name and the CLI command it wraps.
  • Params integration: add a params struct in src/mcp/tools.rs.
  • Runtime wiring: implement a #[tool] method on NucleoServer using the Parameters<T> extractor and execute the CLI with self.run or self.run_owned.
  • Validation: validate config and run cargo check to verify the integration.

Quick Start

Create the new MCP tool by defining its name, wrap the CLI command, add the params struct, implement a #[tool] method on NucleoServer, and run cargo check to verify.

Frequently Asked Questions about add-mcp-tool

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

FAQPage Schema
How do I add a new MCP tool to the nucleo server in Rust?

To add an MCP tool to the nucleo server, you define a tool name, wrap a CLI command, add a params struct in src/mcp/tools.rs, and implement a #[tool] method on NucleoServer using the Parameters<T> extractor.

How does CLI wrapping work when integrating MCP tools with Claude Desktop?

CLI wrapping integrates MCP tools with Claude Desktop by executing wrapped commands through the self.run or self.run_owned methods on the NucleoServer, allowing runtime invocation of the newly wired tool.

What is the process for defining parameters for a new MCP tool integration?

Defining parameters for an MCP tool integration requires adding a params struct in the src/mcp/tools.rs file, which is then utilized by the Parameters<T> extractor within the #[tool] method on the NucleoServer.

How do I validate a newly wired MCP tool in the nucleo server?

You validate a newly wired MCP tool by validating its configuration and running the cargo check command to verify that the Rust integration compiles correctly without errors.

Can I use the Parameters<T> extractor for runtime invocation of MCP tools?

Yes, you can use the Parameters<T> extractor within a #[tool] method on NucleoServer to enable runtime invocation of MCP tools via self.run or self.run_owned.

What are the steps to scaffold a tool for nucleo and Claude Desktop integration?

Scaffolding a tool for nucleo and Claude Desktop integration involves prompting for an explicit tool name, wrapping the desired CLI command, integrating the params struct, and wiring the #[tool] method.