Registry Data Modeling: Normalized Tables vs JSONB Server Versions

[yinebebt]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

We're implementing an MCP registry and can support the server.json spec and version tracking - the question is whether storing server metadata like versions in separate tables is invalid for the registry specs.

Keeping versions in separate tables means we can have version-specific environments where server metadata (name, description) stays unchanged and only new version rows are added.

Normalized Relational Approach:

CREATE TABLE servers (
    id UUID PRIMARY KEY,
    name VARCHAR(255),
    description TEXT,
    repository JSONB,
    created_at TIMESTAMP
);

CREATE TABLE server_versions (
    id UUID PRIMARY KEY,
    server_id UUID REFERENCES servers(id),
    version VARCHAR(50),
    packages JSONB,
    environment_variables JSONB,
    created_at TIMESTAMP
);

Does the MCP registry specification require any specific data storage approach, or is it implementation-agnostic?