quarkus s

This MCP server collection provides a set of Java-based Quarkus MCP servers that extend the Model Context Protocol capabilities. Each server (e.g., jdbc, jvminsight, filesystem, jfx, kubernetes, containers, wolfram) runs under the jbang-enabled workflow and can be started to expose a specific functionality to an MCP-enabled LLM. You can invoke a server using the corresponding jbang command as shown in the repository, which runs the server locally and exposes its MCP endpoints for querying, storage, inspection, or interaction with external systems. The tools cover data storage via JDBC, JVM inspection, filesystem access, JavaFX drawing capabilities, Kubernetes interaction, container engine control, and Wolfram Alpha integration, among others. To use a particular server, run the provided jbang command for that server and then issue MCP requests to the server’s endpoints from your LLM platform or client application.

Note: The README indicates these servers are designed to be launched via jbang (or substitutable equivalents like npx @jbangdev/jbang, uvx jbang, or pipx jbang). Each server’s README describes its specific usage and any required arguments. After launching, you can route relevant MCP queries to that server to perform its tasks (e.g., storing data via JDBC, inspecting a JVM, listing filesystem contents, or launching container commands).

Prerequisites:

• Java (JDK 11+ recommended)
• Maven (for building the multi-module project, if you plan to compile locally)
• JBang (for running the MCP servers via the provided one-liner)

Installation steps:

1. Install Java (JDK 11+): download and install from https://adoptium.net or use your OS package manager.
2. Install Maven (optional if you just run prebuilt servers, but required for building):
   • macOS: brew install maven
   • Linux: sudo apt-get install maven
   • Windows: use the Maven installer from the Apache site
3. Install JBang (required to run the MCP servers as described in the README):
   • Run: curl -Ls https://sh.jbang.dev | bash
   • Add JBang to PATH as instructed by the installer, then reopen your terminal.
4. Verify installation:
   • jbang --version
   • java -version

Running a server:

• The project uses JBang-based commands to start individual MCP servers. For example, to run the jdbc server, you would execute the command provided in the repository (via the jbang command). Since the README indicates you can replace jbang with npx @jbangdev/jbang, uvx jbang, or pipx jbang, you can adapt the one-liner accordingly:

Example (using npx & the jdbc server):

bash npx -y @jbangdev/jbang jdbc@quarkiverse/quarkus-mcp-servers

This will start the jdbc MCP server and expose its endpoints for MCP usage.

Note: The exact command per server is described in each server's README (e.g., jdbc, jvminsight, filesystem, etc.). After starting, you can send MCP requests to the running server from your LLM client or test harness.

Tips and common issues:

• Ensure your Java environment is properly configured and that JAVA_HOME points to a valid JDK.
• When using jbang via npx/uvx/pipx substitutions, verify the alias resolves correctly on your system.
• Each server is described in its own subdirectory README with usage examples; start with the one you need (e.g., jdbc for data persistence or kubernetes for cluster interactions).
• If you encounter network or port conflicts, check that the server ports are free or configure a different port per server as allowed by the server implementation.
• For environment variables, defaults are often shown in the individual server READMEs; you may need to configure JDBC URLs, authentication tokens, or external service endpoints as part of your MCP deployment.
• The project is designed to be extended by adding new servers under the same MCP framework; follow the contributing guide in the repo for adding new server implementations.