Coder Toolbox MCP Server

What is Coder Toolbox MCP Server?

A utility toolkit designed to enhance the interaction between Claude and code, providing seamless integration tools for code analysis, manipulation, and testing workflows. It is built specifically for Java projects, offering operations on test execution logs and Java class files.

How to use Coder Toolbox MCP Server?

Configure the server in your MCP client and invoke its available tools. The server exposes tools for test log retrieval, locating, creating, and modifying Java classes with parameters such as className, sourceType, packagePath, classBody, and edit operations. Use the dryRun parameter on content replacement and deletion to preview changes without applying them.

Key features of Coder Toolbox MCP Server

• Test execution log retrieval and analysis
• Locate Java classes with package and source type filtering
• Create new Java classes with proper package structure
• Add, replace, or delete content in existing Java classes
• Add or delete methods in Java classes
• Add or delete constructors in Java classes

Use cases of Coder Toolbox MCP Server

• Quickly find a Java class in a large project using package filters
• Create a new Java class in the correct source or test directory
• Add a method or constructor to an existing class without manual editing
• Replace specific code snippets in multiple classes with a dry‑run preview
• Delete outdated code from class bodies while reviewing changes

FAQ from Coder Toolbox MCP Server

What operations does Coder Toolbox MCP Server support?

It supports retrieving test execution logs, locating Java classes, creating new classes, and managing class body content (add, replace, delete) including methods and constructors.

What are the current limitations?

According to the roadmap, adding class‑level annotations, interface implementations, class inheritance, organizing imports, and code formatting are not yet implemented.

How are class names matched?

Class names are case‑sensitive. The sourceType and packagePath parameters can restrict the search to source or test directories and a specific package.

Does the server require any external dependencies?

The README does not mention any external dependencies or runtime requirements beyond the MCP protocol.

What happens when I use dryRun on content replacement or deletion?

The class_replace_body and class_delete_body tools accept an optional dryRun boolean. If true, the server returns a diff of the changes without modifying the file.