modelcontextprotocol / modelcontextprotocol/registry
Support JVM packages on maven central
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem? Please describe.
JVM packages are not supported at all.
Describe the solution you'd like
Support JVM packages (i.e. jars) on Maven Central.
Describe alternatives you've considered
N/A
Additional context
Domain ownership of the group ID is already validated by maven central, So ownership can either be done via that (i.e. requiring the MCP name match the group/artifact), or an attribute in the published POM.
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
The issue does not name files or tests. Start by tracing how the registry currently identifies and validates packages, then compare the Maven Central group/artifact and published POM ownership options described here. Done means JVM JAR packages from Maven Central can be registered with an agreed ownership check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100