Tadas Antanavicius
Tadas Antanavicius
Prepared by Claude Code, reviewed by me. > [!IMPORTANT] > **This PR depends on #803 and must be merged after it.** PR #803 decouples the `server.schema.json` versioning from `openapi.yaml` by...
Drafted by Claude Code, reviewed and tested by me. Add instructions for maintainers to connect to the production PostgreSQL database, including Cloud Shell (recommended) and local machine methods, plus read-only...
## What this fixes The API changelog had a section header dated `2025-11-17`, but the openapi.yaml version is `2025-10-17`. This was confusing because they appeared to be tracking the same...
The schema in this repo may contain unreleased changes, so labeling it with a dated version URL is misleading. Change to use a `draft` URL instead, and add documentation for...
Update all documentation to reference the stable `/v0.1/` API version instead of the development `/v0/` version. Didn't update internal references (e.g. in admin-only docs) as that probably make sense to...
From @dsp-ant: > ... I want to make sure people understand that the registry exists and how to use it, by visiting modelcontextprotocol.io ... From @domdomegg: > I think the...
Co-authored with Claude Code, but I've closely reviewed/modified/vetted all changes; ready for final review. ## Summary This PR adds LocalTransport and RemoteTransport separation with URL template variable support for remote...
See: https://github.com/modelcontextprotocol/registry/pull/570/files#r2427093900 There is nothing preventing someone from publishing a server.json with this mistake. Should we validate it at the schema or API level?
Follow on to https://github.com/modelcontextprotocol/registry/pull/570 See https://github.com/modelcontextprotocol/registry/pull/570#issuecomment-3367417636 for the starting point My rough understanding of what we want to accomplish here is to, at minimum: 1) Collect nested variables in the...
I think it would be helpful to encourage (or require?) publishers to include a contact email when publishing a server. This would empower at least a few downstream functionalities for...