devoxxbe-2025

This MCP server provides Java-based demonstrations of building and running an MCP (Model Context Protocol) server using Java tooling and frameworks. The included samples illustrate how to expose primitives such as Tools, Prompts, and Resources as MCP endpoints and how to wire them into a streaming HTTP transport or standard IO streams. With the Docker image configured here, you can quickly spin up a runnable environment to experiment with MCP primitives, test prompts, and observe how responses flow through the MCP runtime. Once running, you can interact with the server to create, query, and manipulate MCP primitives, and you can adapt the examples to your own domain models and back-end logic. The repository also references Java SDKs and various framework integrations (Micronaut, Spring, Quarkus) to help you port or extend the server using the MCP primitives and transports you prefer.

Prerequisites:

• Docker installed and running on your machine
• Basic familiarity with MCP concepts (primitives, tools, prompts, resources)

Installation steps:

1. Pull and run the MCP server container:

   docker pull sdelamo/devoxxbe-2025-mcp-server docker run -i sdelamo/devoxxbe-2025-mcp-server

2. Confirm the server is responding on the container's output or exposed ports (depending on your run options).

3. If you need to customize environment options, you can pass environment variables via docker run, e.g.:

   docker run -i -e JAVA_OPTS="-Xms256m -Xmx1g" sdelamo/devoxxbe-2025-mcp-server

4. For local development without Docker, install Java and run the sample JVM application following the repository’s Java SDK guidance (noted in the README references) to start an MCP server, and ensure it binds to the expected transport (stdio or HTTP/SSE) as demonstrated in the samples.

5. Refer to the repository’s documentation links for framework-specific setup (Micronaut, Spring, Quarkus) if you plan to port or integrate with a particular framework.

Tips and notes:

• The Docker image name used here is based on the repository slug and may be updated; verify the latest image tag on the registry before pulling.
• If you switch transports (stdio vs HTTP/SSE), ensure your client tooling matches the chosen transport.
• When experimenting with primitives, keep an eye on serialization formats and version compatibility between the MCP runtime and the primitives you implement.
• If you encounter memory or startup issues, increase Java heap via JAVA_OPTS (e.g., -Xms512m -Xmx2g) when running in containers.
• If you fork or adapt this server for a real project, consider building a native entrypoint or using framework bootstrappers (Micronaut/Spring/Quarkus) to align with your deployment strategy.