modelcontextprotocol / modelcontextprotocol/java-sdk

Java MCP Server examples are incomplete and non-runnable

Open
#687 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation P3
Dominant language
Java
Stars
3.7k
Forks
1.1k
Avg merge
1d 15h
Merged PRs (30d)
9

Description

Bug description

The current documentation examples for the Java MCP Server are incomplete and non-functional. Dependencies referenced in the code snippets cannot be resolved, and critical components (e.g., main class, configuration, or entry point) are missing. There is no working “Hello World” example to verify basic setup and functionality, making it impossible for new users to get started.

Environment

Spring MCP version: 0.16.0 with webflux implementation
Java version: Java 11
Build tool: Maven
IDE: Eclipse

Steps to reproduce

Go to the official Spring MCP documentation (e.g., https://modelcontextprotocol.io/sdk/java/mcp-server).
Copy the provided code snippets with webflux stateless into a new Java project.
Attempt to compile or run the code.
Observe unresolved dependencies

Expected behavior

The documentation should provide a complete, minimal, and runnable Java example that:

Includes all necessary dependencies (with Maven/Gradle snippets).
Contains a working demo example.
Demonstrates a basic “Hello World” endpoint or service.
Can be copied, pasted, and run immediately without additional research or guessing.
Minimal Complete Reproducible example

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Java MCP Server documentation at https://modelcontextprotocol.io/sdk/java/mcp-server and review the WebFlux stateless snippets, their Maven dependencies, and the missing configuration or entry point. Done means the documentation includes a complete minimal Java 11 Hello World example with resolvable dependencies and enough setup to copy, compile, and run without further research.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.