modelcontextprotocol / modelcontextprotocol/registry

Automatic generation of the schema for server.json

Open
#459 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement v1
Dominant language
Go
Stars
7.3k
Forks
994
Avg merge
4d 12h
Merged PRs (30d)
19

Description

Right now we manually maintain the Go structs that describe the server.json format alongside its schema. This isn’t ideal, since it’s easy for the two to drift out of sync.

A better approach would be to lean on tools that let us define everything at the Go struct level and then auto-generate the schema from there. That way, we reduce errors and keep things consistent with less effort. Let’s take advantage of that.

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 by locating the Go structs that describe the server.json format and the manually maintained schema. Compare their current generation and validation paths, then define a workflow where the schema is generated from the structs and verify that the resulting server.json schema remains consistent without manual duplication.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.