mcp-tool-creator

Generate project-scoped MCP servers exposing docker-compose services as named tools.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill mcp-tool-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tool-creator
Source: https://github.com/nicolas-codemate/claudeCodeConfig/tree/main/skills/mcp-tool-creator
Command: npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill mcp-tool-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a project-scoped MCP server that exposes Docker Compose services as named tools. This enables teams to quickly turn existing docker-compose services into reusable tools within Claude Code.

Core Features & Use Cases

  • Generate a dedicated MCP server per project and register it in .mcp.json.
  • Wrap docker compose exec commands for each service into named tools that can be invoked from Claude Code.
  • Provide templates for Python FastMCP and Node.js SDK to run tools locally.

Quick Start

Say 'create MCP tools for my project' to generate the server and tools.

Frequently Asked Questions about mcp-tool-creator

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

FAQPage Schema
How do I expose docker-compose services as Claude tools?

You can expose docker-compose services as Claude tools by generating a project-scoped MCP server that wraps docker compose exec commands into named tool definitions, which are then registered in the local .mcp.json configuration file.

Can I generate an MCP server from docker-compose using Python or Node.js?

Yes, you can generate an MCP server from docker-compose using either Python FastMCP or Node.js SDK templates, allowing you to run the generated tool wrappers locally within your specific project environment.

What is the best way to turn existing docker-compose services into reusable tools?

The best way to turn docker-compose services into reusable tools is to automate reading the docker-compose.yml file, match services against tool patterns, and generate a dedicated local MCP server per project with safe defaults.

Does generating MCP tools from docker-compose require manual configuration updates?

No, generating MCP tools from docker-compose does not require manual configuration updates because the workflow automatically updates or creates the .mcp.json configuration with safe defaults during the server generation process.

How do I create MCP tools for my project quickly?

To create MCP tools for your project quickly, trigger the generation workflow by saying 'create MCP tools for my project', which reads your docker-compose file and outputs the server code and configuration automatically.