add-tool

Generate TypeScript MCP tool definitions and register them in the project.

148|28|Updated Mar 20, 2025
One-click install
npx skills add https://github.com/cyanheads/mcp-ts-core --skill add-tool-cyanheads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-tool
Source: https://github.com/cyanheads/mcp-ts-core/tree/main/skills/add-tool
Command: npx skills add https://github.com/cyanheads/mcp-ts-core --skill add-tool-cyanheads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold MCP tool definitions quickly to standardize new tools and reduce boilerplate.

Core Features & Use Cases

  • Generates a complete tool definition skeleton including title, description, input/output schemas, and a handler scaffold.
  • Ensures the new tool is registered in the project's tool list or barrel, and aligns with naming conventions.
  • Supports quick iteration for new capabilities or enhancements in MCP servers.

Quick Start

Run the scaffold to generate a new tool definition in your MCP server project.

Frequently Asked Questions about add-tool

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

FAQPage Schema
How do I scaffold MCP tool definitions in a TypeScript project?

To scaffold MCP tool definitions, the tool generates a TypeScript file with a complete skeleton including title, description, input and output schemas, and a handler scaffold under the project's definitions directory.

What is the best way to generate boilerplate code for MCP server tools?

Generating boilerplate for MCP server tools is best handled by scaffolding a complete tool definition skeleton that aligns with naming conventions and automatically updates registration in the project's tool list or barrel.

Does this scaffolding process automatically update the tool registry?

Yes, the scaffolding process automatically updates the tool registry by ensuring the newly generated TypeScript tool definition is registered in the project's tool list or barrel file.

How do I validate frontmatter metadata when creating new MCP tools?

You validate frontmatter metadata when creating new MCP tools by applying a scaffolding process that validates the metadata according to project conventions while generating the tool definition file.

Can I use this to quickly iterate on new capabilities for MCP servers?

Yes, you can use this to quickly iterate on new capabilities for MCP servers by standardizing the creation of new tools and reducing the boilerplate code required for each new tool definition.