create-mcp-tool

Scaffolds new tools for the CodeStar MCP Server with predefined patterns and files.

59|11|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/codescene-oss/codescene-mcp-server --skill create-mcp-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-mcp-tool
Source: https://github.com/codescene-oss/codescene-mcp-server/tree/main/.agents/skills/create-mcp-tool
Command: npx skills add https://github.com/codescene-oss/codescene-mcp-server --skill create-mcp-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new tools for the CodeScene MCP Server by providing a standardized template that enforces project conventions and best practices.

Core Features & Use Cases

  • Boilerplate Generation: Automatically sets up the correct directory structure, __init__.py, and basic implementation files for a new tool.
  • Dependency Injection Pattern: Guides the user in selecting and implementing appropriate dependency injection patterns for testability.
  • Convention Enforcement: Ensures adherence to project standards for decorators, testing, and registration within the MCP server.
  • Use Case: A new contributor needs to add a tool to analyze code complexity. They use this Skill to quickly generate the foundational files and structure, allowing them to focus on the tool's logic.

Quick Start

Use the create-mcp-tool skill to scaffold a new tool named 'code-quality-analyzer'.

Frequently Asked Questions about create-mcp-tool

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

FAQPage Schema
How do I scaffold a new MCP server tool and generate boilerplate code?

To scaffold a new MCP server tool, this Skill automates boilerplate code generation by creating the correct directory structure, __init__.py, implementation, and unit test files following FastMCP framework conventions.

What is the best way to enforce dependency injection patterns when adding tools to an MCP server?

Enforcing dependency injection patterns for MCP server tools is handled by guiding you through selecting and implementing testable injection structures during the automated file generation process.

Do I need to manually register new Python tools within the CodeScene MCP Server project?

You do not need to manually register new Python tools, as this scaffolding process enforces project-specific guidelines for decorators, testing, and automatic registration within the MCP server.

Does the scaffolding process generate unit tests for new MCP server tools?

The scaffolding process does generate unit tests, automatically creating Python test files alongside the implementation files to ensure adherence to established testing conventions.

Can I use this to generate directory structures for any Python code generation project?

You cannot use this for general Python code generation, as it specifically scaffolds tools for the CodeScene MCP Server project and enforces its established directory structure and FastMCP framework conventions.