mcp-tool-scaffold

Scaffold an end-to-end MCP tool across subsystem code, wrappers, and documentation.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/arashshahidi1997/projio --skill mcp-tool-scaffold
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tool-scaffold
Source: https://github.com/arashshahidi1997/projio/tree/main/docs/prompts/skills/mcp-tool-scaffold
Command: npx skills add https://github.com/arashshahidi1997/projio --skill mcp-tool-scaffold

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a complete end-to-end MCP tool workflow: implement the function in the target subsystem, create the MCP wrapper, register the tool in the server, and update agent instructions across the repo to ensure discoverability and correct routing.

Core Features & Use Cases

  • End-to-end scaffold for a new MCP tool spanning code, wrappers, server integration, and documentation.
  • Ensures consistent patterns across subsystems (biblio, codio, notio, pipeio, indexio, figio) and agents can discover tools reliably.
  • Provides an implement-by-wrapping workflow that reduces setup time for new tooling and minimizes integration errors.

Quick Start

Run the scaffold by providing TOOL_NAME, PACKAGE, and DESCRIPTION to generate the complete MCP tool skeleton and integration steps.

Frequently Asked Questions about mcp-tool-scaffold

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

FAQPage Schema
How do I scaffold an end-to-end MCP tool for a projio subsystem?

To scaffold an MCP tool, provide the TOOL_NAME, PACKAGE, and DESCRIPTION to generate the complete skeleton. The process coordinates implementation in the subsystem package, wrapper creation, server registration, and documentation updates.

What is the process for registering a new MCP tool in the server?

Registering an MCP tool involves creating a projio.mcp wrapper for the subsystem function and adding the tool to server.py. This ensures the tool is correctly routed and discoverable by agents across the project.

Do I need to update agent instructions when adding an MCP tool to my project?

Yes, updating agent instructions like CLAUDE.md is required when adding an MCP tool. This ensures agents can discover the tool reliably and route requests to the correct subsystem wrapper.

Can I use this scaffold for any subsystem package like codio or notio?

Yes, this scaffold applies to any projio subsystem package, including biblio, codio, notio, pipeio, indexio, and figio. It enforces consistent integration patterns and wrapper delegation across all subsystems.

What's the best way to minimize integration errors when wiring a new MCP tool?

The best way to minimize integration errors is using an implement-by-wrapping workflow that follows existing project patterns. This reduces setup time by automating code integration, server registration, and routing updates.

Why does my MCP tool wrapper need to delegate to the subsystem package?

The MCP tool wrapper delegates to the subsystem package to maintain separation of concerns and follow existing project patterns. This ensures the core implementation remains within the correct subsystem while the wrapper handles MCP protocol integration.