MinecraftDev

MinecraftDev is an IntelliJ plugin project aimed at enhancing Minecraft development workflows within the IDE. This MCP server configuration points to a Node-based server entry (placeholder path) that would typically expose tooling and commands related to building, testing, and generating resources for the MinecraftDev plugin. In practice, you would use the server to manage and run tasks such as generating code stubs, validating project structure, and orchestrating Gradle-based tasks from the MCP server layer. If you connect to this server in your MCP-oriented environment, you can leverage the provided tooling to streamline plugin development, build distributions, and run Ide-based tests.

To use the tools, ensure your environment has a compatible Java and Gradle setup, then start the MCP server via the configured command. From there, invoke available commands (e.g., generate, build, runIde) as exposed by the server adapter. The tooling is designed to integrate with Gradle and the IntelliJ plugin lifecycle, so expect commands that trigger Gradle tasks, code generation steps, and IDE run configurations for testing the MinecraftDev plugin.

Prerequisites

• Java Development Kit 21 (OpenJDK 21 recommended)
• Gradle (wrapper in the project is usually used)
• Git
• Node.js runtime if the server entry point is Node-based (as per mcp_config, placeholder)

Installation steps

1. Install Java JDK 21 on your system:

   • macOS: brew install temurin
   • Windows: use the installer from Temurin
   • Linux: sudo apt-get install temurin-21-jdk

2. Install Gradle (if not using the Gradle wrapper):

   • Follow instructions at https://gradle.org/install/

3. Clone the repository: git clone https://github.com/minecraft-dev/MinecraftDev.git cd MinecraftDev

4. If using the MCP server as a Node-based entry (as configured), ensure Node.js is installed:

   • macOS: brew install node
   • Windows: https://nodejs.org/
   • Linux: sudo apt-get install nodejs npm

5. Install and start the MCP server (example using the configured entry):

   • npm-based or node-based startup would be invoked in an environment where the server.js path is resolved.
   • If using the provided Gradle tasks for the plugin, you can build and run within IntelliJ as per the project's Gradle instructions, e.g.:

   ./gradlew build ./gradlew runIde

6. Verify the plugin runs in the IDE and the tooling exposes the expected tasks like generate, build, and runIde.

Tips and common issues:

• Ensure JAVA_HOME points to a Java 21 JDK when building or running Gradle tasks for the MinecraftDev plugin.
• The MCP server configuration above uses a placeholder Node-based entry path. If you transition to a real server, replace with the actual server entry (path/to/server.js) or switch to a native startup command appropriate for your deployment environment.
• If you encounter Gradle wrapper issues, run ./gradlew wrapper to refresh the wrapper scripts.
• When using IntelliJ, install the MinecraftDev plugin from the JetBrains repository as described in the repository's Installation section to ensure compatibility.
• Network/proxy settings may affect dependency resolution; configure Gradle and Node/npm proxy settings if needed.
• Environment variables like JAVA_HOME and GRADLE_OPTS can influence memory allocation and tool behavior; tune them if you see out-of-memory or startup issues.