modelcontextprotocol / modelcontextprotocol/java-sdk
Migrate the reference & APIs docs to the java-sdk project
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.7k
- Forks
- 1.1k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 9
Description
For historical reasons, the MCP Java SDK has been maintained inside the main MCP docs and deployed with the main docs
However in accordance with latest SDK guidelines we need to standardize documentation structure across SDKs using native/idiomatic doc generators - key elements: conformance score in README, documentation in docs folder, standardized sections
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing documentation under main/docs/sdk/java and comparing it with the java-sdk repository structure. Check the SDK guidelines in issue #2144 for the required README conformance score, docs folder, and standardized sections. The work is done when the Java SDK reference and API documentation are migrated and follow those conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100