solon

Solon is a Java enterprise application framework designed for full-scenario development. This MCP server wraps a Solon-based runtime, allowing you to run the Solon application with a standard Java command. Use the provided tools to start the Solon server, monitor startup logs, and access framework features such as dependency injection, AOP, and flexible configuration. Ensure your environment has a compatible JDK (Java 8 through Java 25 as indicated by the project) and that solon.jar is available in your working directory. To operate, start the server via the mcp_config entry and connect to any deployed endpoints or admin interfaces exposed by your Solon application.

Prerequisites:

• Java Development Kit (JDK) 8, 11, 17, or 21+ (as supported by Solon) installed on your machine.
• A build of Solon (solon.jar) or a packaged application that includes the Solon runtime.

Step-by-step:

1. Install JDK:
   • Download and install a supported JDK from the official sources.
   • Ensure java -version reports a compatible version.
2. Obtain solon.jar:
   • Build the Solon project from the repository, or download a pre-built solon.jar for your environment.
   • Place solon.jar in a suitable directory (e.g., /opt/solon/solon.jar).
3. Prepare environment (optional but recommended):
   • Set JAVA_HOME to your JDK path.
   • Create a minimal config if needed via environment variables (see additional notes).
4. Run the MCP server entry (example):
   • Use the mcp_config configuration to start the server via your MCP runner. If launching manually, run: java -jar solon.jar
5. Verify:
   • Check the console logs for successful startup messages.
   • Access application endpoints as defined by your Solon project (e.g., http://localhost:port/).

Notes:

• If you are packaging as a container, you can adapt the command to your container runtime, e.g., docker run -i solon:latest, adjusting the entrypoint to run java -jar solon.jar.

Tips and common issues:

• Ensure JAVA_HOME is correctly set; Solon requires a compatible JDK version as shown in the readme.
• If you upgrade Java versions, rebuild solon.jar if your project relies on newer language features.
• For production, consider setting environment variables to configure Solon runtime behavior (SOLON_ENV, logging levels, etc.).
• If the server fails to start due to port conflicts, adjust port settings in your Solon application configuration.
• When integrating with MCP tooling, keep the mcp_config entry up to date with the actual command and path to solon.jar in your deployment environment.