mcp-tool-generator

Generate MCP tools for GitLab operations with standardized TypeScript patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/daispacy/py-claude-marketplace --skill mcp-tool-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tool-generator
Source: https://github.com/daispacy/py-claude-marketplace/tree/main/py-plugin/skills/mcp-tool-generator
Command: npx skills add https://github.com/daispacy/py-claude-marketplace --skill mcp-tool-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires .

What problem does it solve?

This Skill generates new MCP tools and templates following standardized TypeScript patterns, enabling rapid creation of GitLab integrations with proper error handling, schemas, and API calls.

Core Features & Use Cases

  • Tool scaffolding: Create CRUD and multi-action MCP tools with consistent structure.
  • Complex operations: Support multi-action tools and advanced operation patterns.
  • Registration templates: Produce ready-to-register TypeScript files and example usage.

Quick Start

Request: "I need a new MCP tool that manages issues." The tool will generate a TypeScript tool scaffold named like gitlab-manage-issue.ts with a corresponding registrar function.

Frequently Asked Questions about mcp-tool-generator

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

FAQPage Schema
How do I generate MCP tools for GitLab automation?

Generate MCP tools by requesting a new tool for your GitLab operation—the tool creates TypeScript files with standardized patterns, including Zod schemas, error handling, and GitLab API integration following kebab-case naming conventions.

Can I create CRUD and multi-action MCP tools with consistent structure?

Yes, this tool scaffolds both simple CRUD operations and complex multi-action tools with consistent TypeScript patterns, registration functions in PascalCase, and ready-to-use example implementations.

What does the generated MCP tool template include?

Generated templates include TypeScript file structure, input validation schemas, robust error handling, GitLab API calls, registration functions, and example usage—all following the project's standardized pattern.

Do I need to manually write schemas and error handling for GitLab tools?

No, the tool automatically generates Zod schemas for input validation and integrated error handling as part of the TypeScript scaffold, eliminating manual boilerplate for GitLab integrations.

How does tool naming work in the generated MCP files?

Generated tools use kebab-case for file names (e.g., `gitlab-manage-issue.ts`) with corresponding PascalCase registration functions, following standardized naming patterns automatically.