modelcontextprotocol / modelcontextprotocol/registry
Remove MCP Registry-specific _meta fields from generic API spec
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Similarly to #459
Right now, we manually maintain the OpenAPI spec manually. A better approach would be to rely on tools that let us define everything at the code level and then auto-generate the OpenAPI spec from there. That way, we reduce errors and keep things consistent with less effort. Let’s take advantage of that.
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 manually maintained OpenAPI spec and the related work in #459. Identify which _meta fields are MCP Registry-specific, then evaluate a code-level source and generation workflow; done means the generic API spec no longer contains those fields and the specification can be regenerated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, openapi
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100