Skip to content

Document server.json #90

Description

@tadasant

We have a starting point for this, but we should:

  • Formally define what is and is not valid in this JSON
  • Make sure we have some mechanism for versioning the schema, because it's very likely to evolve over time (especially as non-registry initiatives start to prioritize defining the notion of static server data)

Activity

  1. added
    go-live blockerThis issue is one we need to address prior to initial go-live
    on May 27, 2025
  2. tadasant commented on Jun 25, 2025

    @tadasant
    MemberAuthor

    Note: we should be thoughtful about how to define version as per https://github.com/modelcontextprotocol/registry/pull/134/files#r2145287494

  3. tadasant commented on Jun 25, 2025

    @tadasant
    MemberAuthor

    Also make sure the schema itself is versioned: #139

  4. domdomegg commented on Aug 20, 2025

    @domdomegg
    Member

    Note: we should be thoughtful about how to define version as per https://github.com/modelcontextprotocol/registry/pull/134/files#r2145287494

    Discussion continuing on this in #158

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    go-live blockerThis issue is one we need to address prior to initial go-liveproduct requirements workUpstream of development work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions