Skip to content

Separate out Registry-specific server.json out from generic server.json #155

Closed
#167
Closed
Separate out Registry-specific server.json out from generic server.json#155
#167
Assignees
tadasant
Labels
go-live blockerThis issue is one we need to address prior to initial go-liveproduct requirements workUpstream of development workserver.json

Description

@tadasant
tadasant
opened on Jun 28, 2025

Analogous to #149, we should have a (more constrained) schema for the official Registry vs. a generic server.json that will serve other use cases.

See comment: https://github.com/modelcontextprotocol/registry/pull/153/files/8041f5f359d241862a5de1ddc8574fe79c4c44b0#r2172966211

Related: #153

Activity

  1. tadasant
    added
    go-live blockerThis issue is one we need to address prior to initial go-live
    product requirements workUpstream of development work
    on Jun 28, 2025
  2. tadasant
    self-assigned this
    on Jun 30, 2025
  3. tadasant
    added
    server.json
    on Jun 30, 2025
  4. tadasant
    closed this as completedin #167on Jul 9, 2025
  5. tadasant
    added a commit that references this issue on Jul 9, 2025

    Split "general" server.json from "registry-specific" server.json (#167)

    a5f417b
  6. domdomegg
    added a commit that references this issue on Aug 7, 2025

    Split "general" server.json from "registry-specific" server.json (#167)

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

Metadata

Metadata

Assignees

Labels

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions