chore: Release server.json schema version 2025-12-11

tadasant · claude · tadasant · commit 772bfde612ad · 2025-12-11T09:48:33.000-08:00
This release introduces LocalTransport/RemoteTransport with URL template variables (#570). Key Changes: - New LocalTransport type for packages (non-breaking rename) - New RemoteTransport type with `variables` property for URL templating - URL template variables using {curly_braces} notation - Pattern validation for URLs allowing template variables Schema version: 2025-10-17 → 2025-12-11 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
diff --git a/cmd/publisher/commands/publish_test.go b/cmd/publisher/commands/publish_test.go
@@ -44,8 +44,8 @@ func TestPublishCommand_DeprecatedSchema(t *testing.T) {
 			errorSubstr: "deprecated schema detected",
 		},
 		{
-			name:        "current 2025-10-17 schema should pass validation",
-			schema:      "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+			name:        "current 2025-12-11 schema should pass validation",
+			schema:      "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
 			expectError: false,
 		},
 		{
diff --git a/data/seed.json b/data/seed.json
@@ -1,6 +1,6 @@
 [
   {
-    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
     "name": "io.github.domdomegg/airtable-mcp-server",
     "description": "Read and write access to Airtable database schemas, tables, and records.",
     "repository": {
@@ -62,7 +62,7 @@
     ]
   },
   {
-    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
     "name": "io.github.domdomegg/airtable-mcp-server",
     "description": "Read and write access to Airtable database schemas, tables, and records.",
     "repository": {
@@ -115,7 +115,7 @@
     ]
   },
   {
-    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
     "name": "io.github.domdomegg/time-mcp-nuget",
     "description": "Get the current UTC time in RFC 3339 format.",
     "repository": {
@@ -136,7 +136,7 @@
     ]
   },
   {
-    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
     "name": "io.github.domdomegg/time-mcp-pypi",
     "description": "Get the current UTC time in RFC 3339 format.",
     "repository": {
diff --git a/docs/modelcontextprotocol-io/package-types.mdx b/docs/modelcontextprotocol-io/package-types.mdx
@@ -15,7 +15,7 @@ npm packages use `"registryType": "npm"` in `server.json`. For example:
 
 ```json server.json highlight={9}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/email-integration-mcp",
   "title": "Email Integration",
   "description": "Send emails and manage email accounts",
@@ -53,7 +53,7 @@ PyPI packages use `"registryType": "pypi"` in `server.json`. For example:
 
 ```json server.json highlight={9}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/database-query-mcp",
   "title": "Database Query",
   "description": "Execute SQL queries and manage database connections",
@@ -91,7 +91,7 @@ NuGet packages use `"registryType": "nuget"` in `server.json`. For example:
 
 ```json server.json highlight={9}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/azure-devops-mcp",
   "title": "Azure DevOps",
   "description": "Manage Azure DevOps work items and pipelines",
@@ -135,7 +135,7 @@ Docker/OCI images use `"registryType": "oci"` in `server.json`. For example:
 
 ```json server.json highlight={9}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/kubernetes-manager-mcp",
   "title": "Kubernetes Manager",
   "description": "Deploy and manage Kubernetes resources",
@@ -170,7 +170,7 @@ MCPB packages use `"registryType": "mcpb"` in `server.json`. For example:
 
 ```json server.json highlight={9}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/image-processor-mcp",
   "title": "Image Processor",
   "description": "Process and transform images with various filters",
diff --git a/docs/modelcontextprotocol-io/quickstart.mdx b/docs/modelcontextprotocol-io/quickstart.mdx
@@ -143,7 +143,7 @@ Open the generated `server.json` file, and you should see contents like:
 
 ```json server.json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.my-username/weather",
   "description": "An MCP server for weather information.",
   "repository": {
@@ -177,7 +177,7 @@ Edit the contents as necessary:
 
 ```diff server.json
  {
-   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "name": "io.github.my-username/weather",
    "description": "An MCP server for weather information.",
    "repository": {
diff --git a/docs/modelcontextprotocol-io/registry-aggregators.mdx b/docs/modelcontextprotocol-io/registry-aggregators.mdx
@@ -75,7 +75,7 @@ The subregistry OpenAPI spec allows subregistries to inject custom metadata via
 
 ```json server.json highlight={17-26}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/email-integration-mcp",
   "title": "Email Integration",
   "description": "Send emails and manage email accounts",
diff --git a/docs/modelcontextprotocol-io/remote-servers.mdx b/docs/modelcontextprotocol-io/remote-servers.mdx
@@ -7,7 +7,7 @@ The MCP Registry supports remote MCP servers via the `remotes` property in `serv
 
 ```json server.json highlight={7-12}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "com.example/acme-analytics",
   "title": "ACME Analytics",
   "description": "Real-time business intelligence and reporting platform",
@@ -31,7 +31,7 @@ Specify the transport by setting the `type` property of the `remotes` entry to e
 
 ```json server.json highlight={9,13}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "com.example/acme-analytics",
   "title": "ACME Analytics",
   "description": "Real-time business intelligence and reporting platform",
@@ -55,7 +55,7 @@ MCP clients can be instructed to send specific HTTP headers by adding the `heade
 
 ```json server.json highlight={11-18}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "com.example/acme-analytics",
   "title": "ACME Analytics",
   "description": "Real-time business intelligence and reporting platform",
@@ -83,7 +83,7 @@ The `remotes` property can coexist with the `packages` property in `server.json`
 
 ```json server.json highlight={7-22}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/email-integration-mcp",
   "title": "Email Integration",
   "description": "Send emails and manage email accounts",
diff --git a/docs/modelcontextprotocol-io/versioning.mdx b/docs/modelcontextprotocol-io/versioning.mdx
@@ -7,7 +7,7 @@ MCP servers **MUST** define a version string in `server.json`. For example:
 
 ```json server.json highlight={6}
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.username/email-integration-mcp",
   "title": "Email Integration",
   "description": "Send emails and manage email accounts",
diff --git a/docs/reference/api/openapi.yaml b/docs/reference/api/openapi.yaml
@@ -728,7 +728,7 @@ components:
           type: string
           format: uri
           description: JSON Schema URI for this server.json format
-          example: "https://static.modelcontextprotocol.io/schemas/draft/server.schema.json"
+          example: "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json"
         packages:
           type: array
           items:
diff --git a/docs/reference/server-json/CHANGELOG.md b/docs/reference/server-json/CHANGELOG.md
@@ -16,6 +16,34 @@ When ready for release, changes in this section will be moved to a dated version
 
 ---
 
+## 2025-12-11
+
+### Changed
+
+#### URL Template Variables for Remote Servers ([#570](https://github.com/modelcontextprotocol/registry/pull/570))
+
+Remote servers can now define URL template variables using `{curly_braces}` notation. This enables multi-tenant deployments where a single server definition can support multiple endpoints with configurable values.
+
+**Example:**
+```json
+{
+  "remotes": [{
+    "type": "streamable-http",
+    "url": "https://{tenant_id}.api.example.com/mcp",
+    "variables": {
+      "tenant_id": {
+        "description": "Your tenant identifier",
+        "isRequired": true
+      }
+    }
+  }]
+}
+```
+
+**Migration:** No changes required. Existing servers continue to work unchanged.
+
+---
+
 ## 2025-10-17
 
 ### Changed
diff --git a/docs/reference/server-json/generic-server-json.md b/docs/reference/server-json/generic-server-json.md
@@ -38,7 +38,7 @@ When publishing to the official registry, custom metadata must be placed under t
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol.anonymous/brave-search",
   "description": "MCP server for Brave Search API integration",
   "title": "Brave Search",
@@ -85,7 +85,7 @@ For MCP servers located within a subdirectory of a larger repository (monorepo s
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol/everything",
   "description": "MCP server that exercises all the features of the MCP protocol",
   "title": "Everything",
@@ -124,7 +124,7 @@ Suppose your MCP server application requires a `mcp start` CLI arguments to star
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.joelverhagen/knapcode-samplemcpserver",
   "description": "Sample NuGet MCP server for a random number and random weather",
   "version": "0.4.0-beta",
@@ -168,7 +168,7 @@ This will essentially instruct the MCP client to execute `dnx Knapcode.SampleMcp
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.modelcontextprotocol/filesystem",
   "description": "Node.js server implementing Model Context Protocol (MCP) for filesystem operations.",
   "title": "Filesystem",
@@ -268,7 +268,7 @@ This will essentially instruct the MCP client to execute `dnx Knapcode.SampleMcp
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol.anonymous/mcp-fs",
   "description": "Cloud-hosted MCP filesystem server",
   "repository": {
@@ -302,7 +302,7 @@ This will essentially instruct the MCP client to execute `dnx Knapcode.SampleMcp
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.example/weather-mcp",
   "description": "Python MCP server for weather data access",
   "title": "Weather",
@@ -358,7 +358,7 @@ The `dnx` tool ships with the .NET 10 SDK, starting with Preview 6.
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.joelverhagen/knapcode-samplemcpserver",
   "description": "Sample NuGet MCP server for a random number and random weather",
   "repository": {
@@ -407,7 +407,7 @@ The `dnx` tool ships with the .NET 10 SDK, starting with Preview 6.
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.example/database-manager",
   "description": "MCP server for database operations with support for multiple database types",
   "repository": {
@@ -516,7 +516,7 @@ The `dnx` tool ships with the .NET 10 SDK, starting with Preview 6.
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol.anonymous/hybrid-mcp",
   "description": "MCP server available as both local package and remote service",
   "title": "Hybrid",
@@ -602,7 +602,7 @@ The `dnx` tool ships with the .NET 10 SDK, starting with Preview 6.
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol/text-editor",
   "description": "MCP Bundle server for advanced text editing capabilities",
   "title": "Text Editor",
@@ -645,7 +645,7 @@ Some CLI tools bundle an MCP server, without a standalone MCP package or a publi
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.snyk/cli-mcp",
   "description": "MCP server provided by the Snyk CLI",
   "title": "Snyk",
@@ -680,7 +680,7 @@ For MCP servers that follow a custom installation path or are embedded in applic
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol.anonymous/embedded-mcp",
   "description": "MCP server embedded in a Desktop app",
   "websiteUrl": "https://anonymous.modelcontextprotocol.io/embedded-mcp-guide",
@@ -695,7 +695,7 @@ This example demonstrates URL templating for remote servers, useful for multi-te
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol.anonymous/multi-tenant-server",
   "description": "MCP server with configurable remote endpoint",
   "title": "Multi-Tenant Server",
@@ -721,7 +721,7 @@ The same URL templating works with SSE transport:
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.modelcontextprotocol.anonymous/events-server",
   "description": "MCP server using SSE with tenant-specific endpoints",
   "version": "1.0.0",
@@ -746,7 +746,7 @@ This example demonstrates URL templating for local/package servers, where variab
 
 ```json
 {
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.example/configurable-server",
   "description": "Local MCP server with configurable port",
   "title": "Configurable Server",
diff --git a/docs/reference/server-json/server.schema.json b/docs/reference/server-json/server.schema.json
@@ -404,7 +404,7 @@
       "properties": {
         "$schema": {
           "description": "JSON Schema URI for this server.json format",
-          "example": "https://static.modelcontextprotocol.io/schemas/draft/server.schema.json",
+          "example": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
           "format": "uri",
           "type": "string"
         },
diff --git a/pkg/api/v0/types.go b/pkg/api/v0/types.go
@@ -32,7 +32,7 @@ type ServerMeta struct {
 }
 
 type ServerJSON struct {
-	Schema      string            `json:"$schema" required:"true" minLength:"1" format:"uri" doc:"JSON Schema URI for this server.json format" example:"https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json"`
+	Schema      string            `json:"$schema" required:"true" minLength:"1" format:"uri" doc:"JSON Schema URI for this server.json format" example:"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json"`
 	Name        string            `json:"name" minLength:"3" maxLength:"200" pattern:"^[a-zA-Z0-9.-]+/[a-zA-Z0-9._-]+$" doc:"Server name in reverse-DNS format. Must contain exactly one forward slash separating namespace from server name." example:"io.github.user/weather"`
 	Description string            `json:"description" minLength:"1" maxLength:"100" doc:"Clear human-readable explanation of server functionality." example:"MCP server providing weather data and forecasts via OpenWeatherMap API"`
 	Title       string            `json:"title,omitempty" minLength:"1" maxLength:"100" doc:"Optional human-readable title or display name for the MCP server." example:"Weather API"`
diff --git a/pkg/model/constants.go b/pkg/model/constants.go
@@ -36,7 +36,7 @@ const (
 // Schema versions
 const (
 	// CurrentSchemaVersion is the current supported schema version date
-	CurrentSchemaVersion = "2025-10-17"
+	CurrentSchemaVersion = "2025-12-11"
 	// CurrentSchemaURL is the full URL to the current schema
 	CurrentSchemaURL = "https://static.modelcontextprotocol.io/schemas/" + CurrentSchemaVersion + "/server.schema.json"
 )

Original file line number	Diff line number	Diff line change
`@@ -44,8 +44,8 @@ func TestPublishCommand_DeprecatedSchema(t *testing.T) {`
`44`	`44`	`errorSubstr: "deprecated schema detected",`
`45`	`45`	`},`
`46`	`46`	`{`
`47`		`- name: "current 2025-10-17 schema should pass validation",`
`48`		`- schema: "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`47`	`+ name: "current 2025-12-11 schema should pass validation",`
	`48`	`+ schema: "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`49`	`49`	`expectError: false,`
`50`	`50`	`},`
`51`	`51`	`{`
Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`[`
`2`	`2`	`{`
`3`		`- "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`3`	`+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`4`	`4`	`"name": "io.github.domdomegg/airtable-mcp-server",`
`5`	`5`	`"description": "Read and write access to Airtable database schemas, tables, and records.",`
`6`	`6`	`"repository": {`
`@@ -62,7 +62,7 @@`
`62`	`62`	`]`
`63`	`63`	`},`
`64`	`64`	`{`
`65`		`- "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`65`	`+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`66`	`66`	`"name": "io.github.domdomegg/airtable-mcp-server",`
`67`	`67`	`"description": "Read and write access to Airtable database schemas, tables, and records.",`
`68`	`68`	`"repository": {`
`@@ -115,7 +115,7 @@`
`115`	`115`	`]`
`116`	`116`	`},`
`117`	`117`	`{`
`118`		`- "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`118`	`+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`119`	`119`	`"name": "io.github.domdomegg/time-mcp-nuget",`
`120`	`120`	`"description": "Get the current UTC time in RFC 3339 format.",`
`121`	`121`	`"repository": {`
`@@ -136,7 +136,7 @@`
`136`	`136`	`]`
`137`	`137`	`},`
`138`	`138`	`{`
`139`		`- "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`139`	`+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`140`	`140`	`"name": "io.github.domdomegg/time-mcp-pypi",`
`141`	`141`	`"description": "Get the current UTC time in RFC 3339 format.",`
`142`	`142`	`"repository": {`
Original file line number	Diff line number	Diff line change
`@@ -75,7 +75,7 @@ The subregistry OpenAPI spec allows subregistries to inject custom metadata via`
`75`	`75`
`76`	`76`	```json server.json highlight={17-26}
`77`	`77`	`{`
`78`		`- "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`78`	`+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`79`	`79`	`"name": "io.github.username/email-integration-mcp",`
`80`	`80`	`"title": "Email Integration",`
`81`	`81`	`"description": "Send emails and manage email accounts",`
Original file line number	Diff line number	Diff line change
@@ -7,7 +7,7 @@ MCP servers MUST define a version string in `server.json`. For example:
`7`	`7`
`8`	`8`	```json server.json highlight={6}
`9`	`9`	`{`
`10`		`- "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",`
	`10`	`+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",`
`11`	`11`	`"name": "io.github.username/email-integration-mcp",`
`12`	`12`	`"title": "Email Integration",`
`13`	`13`	`"description": "Send emails and manage email accounts",`