modelcontextprotocol / modelcontextprotocol/registry
Include ServerCapabilities in server.json
Open
Nobody has claimed this yet.
not go-live blocker
v1
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Feels like a nice-to-have, but it would make sense to allow for ServerCapabilities to be included in server.json data that can get surfaced back to API consumers.
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 with ServerCapabilities in the linked schema.ts and trace how server.json data is handled and surfaced to API consumers. Confirm the expected capability shape, then verify that server.json entries can include it and that the API response exposes it correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100