MCP Clean Code

🚀 MCP Code Cleaning Tool

An MCP server implementation that provides a tool for planning and creating clean, well-structured code with comprehensive English comments.

🚀 Quick Start

The MCP Code Cleaning Tool is designed to assist in planning and creating high - quality code. It offers a range of features and a useful tool named cleancode to ensure your code adheres to clean code principles.

✨ Features

• Plan the code architecture step - by - step.
• Design modular and maintainable components.
• Follow clean code principles and best practices.
• Create code with comprehensive documentation using English comments.
• Re - evaluate design decisions when requirements become clearer.
• Branch to alternative implementation strategies.
• Focus on code readability and conciseness.

📦 Installation

Using with Claude Desktop

Add the following content to claude_desktop_config.json:

npm Installation

{
  "mcpServers": {
    "cleancode": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-clean-code"
      ]
    }
  }
}

Manual Installation

# Install using npm
npm install -g mcp-clean-code

# Then use in the configuration
{
  "mcpServers": {
    "cleancode": {
      "command": "mcp-clean-code"
    }
  }
}

PNPM Installation

# Install using PNPM
pnpm add -g mcp-clean-code

# Then use in the configuration
{
  "mcpServers": {
    "cleancode": {
      "command": "mcp-clean-code"
    }
  }
}

Docker

{
  "mcpServers": {
    "cleancode": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i"
      ]
    }
  }
}

💻 Usage Examples

Basic Usage

The cleancode tool promotes clean code planning by focusing on readability, maintainability, and well - structured English comments.

Input:

• thought (string): The current code planning step.
• nextThoughtNeeded (boolean): Whether another code planning step is needed.
• thoughtNumber (integer): The current step number.
• totalThoughts (integer): The estimated total number of steps.
• isRevision (boolean, optional): Whether to reconsider a previous planning step.
• revisesThought (integer, optional): The number of the step being reconsidered.
• branchFromThought (integer, optional): The step number of the branching point for an alternative method.
• branchId (string, optional): The identifier for the alternative implementation.
• needsMoreThoughts (boolean, optional): Whether more planning steps are needed.

📚 Documentation

Use Cases

The Clean Code tool is suitable for:

• Before writing complex code that requires careful planning.
• When designing new features or refactoring existing code.
• When code structure and organization are crucial.
• To ensure comprehensive documentation with English comments.
• To follow clean code principles and best practices.
• To break down complex functions into modular components.
• To plan testable and maintainable implementations.