microcks

This MCP server provides an HTTP-based interface to interact with a Microcks instance from an MCP client or agent. It exposes MCP endpoints over HTTP (and SSE/streamable variants) so clients can perform actions such as listing, creating, or updating resources exposed by Microcks via the MCP protocol. The server is packaged as a Java Quarkus application and can be run either directly in a Java environment or via Docker. Once the server is running, you can connect your MCP client to the HTTP transport endpoints and start exchanging MCP messages in real time.

By default the server exposes two transport endpoints: a standard streamable HTTP MCP endpoint at /mcp and a server-sent events (SSE) endpoint at /mcp/sse. The MCP server includes support for common MCP message types used to manage Microcks resources (e.g., greetings, capabilities, and CRUD-like interactions against Microcks entities). When running behind a proxy or in a container orchestrator, ensure network access to the host/port where the MCP HTTP transport is exposed and enable CORS if you are calling from a browser or a front-end client.

Prerequisites:

• Java 25 (as used by Microcks MCP Server)
• Docker (optional for containerized runs)
• Optional: Maven wrapper if you want to run locally from source

Option A — Run with Docker

1. Install Docker on your system.
2. Start the MCP server container (example image name; adjust as needed): docker run -i --rm -p 8080:8080 microcks/microcks-mcp-server
3. Verify the server is running by accessing the MCP endpoints at http://localhost:8080/mcp

Option B — Run locally (Java) from source

1. Install JDK 25+ and Maven wrapper (mvnw) available in the project.
2. Clone the repository and navigate to the project root.
3. Start the server locally: ./mvnw clean quarkus:dev
4. Confirm the server is listening on http://localhost:8080 and that MCP endpoints are available at http://localhost:8080/mcp

Option C — Configure a quick environment (optional)

• If deploying behind a reverse proxy or in CI, set QUARKUS_HTTP_PORT and enable CORS as needed.
• Example environment variables: QUARKUS_HTTP_PORT=8080 QUARKUS_HTTP_CORS_ENABLED=true

Tips and common considerations:

• The MCP server in Microcks is Java-based (Quarkus). If you are deploying in Kubernetes or Docker, make sure the container ports are properly mapped to the host.
• The MCP HTTP transport endpoints include a standard streamable endpoint at /mcp and an SSE endpoint at /mcp/sse. If you call from a browser or an SPA, enable CORS (QUARKUS_HTTP_CORS_ENABLED=true).
• Port configuration can be customized via environment variables (e.g., QUARKUS_HTTP_PORT). If you run behind a proxy, ensure the proxy forwards websocket/SSE connections if you use SSE.
• Default authentication and authorization depend on your Microcks setup; configure any required security credentials or tokens as part of your MCP client requests.
• If you see connectivity issues, check container logs or local server logs for MCP endpoint readiness messages like "Listening on: http://localhost:8080".