merge upstream/main, make lastModified a Unix epoch timestamp

Author: salman1993

.gitattributes

@@ -1 +1,2 @@
 package-lock.json linguist-generated=true
+schema/*/schema.json linguist-generated=true

.github/workflows/main.yml

@@ -11,7 +11,7 @@ jobs:
 
     steps:
       - uses: actions/checkout@v4
-      - uses: actions/setup-node@v2
+      - uses: actions/setup-node@v4
         with:
           node-version: 20
           cache: npm

.github/workflows/markdown-format.yml

@@ -4,23 +4,25 @@ on:
   push:
     paths:
       - '**/*.md'
+      - '**/*.mdx'
   pull_request:
     paths:
       - '**/*.md'
+      - '**/*.mdx'
 
 jobs:
   format:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      
+
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
           node-version: '20'
-          
+
       - name: Install dependencies
         run: npm ci
-        
+
       - name: Check markdown formatting
-        run: npm run format:check
+        run: npm run format:check

.github/workflows/site.yml

@@ -10,8 +10,7 @@ The following software is required to work on the spec:
 - Node.js 20 or above
 - TypeScript
 - TypeScript JSON Schema (for generating JSON schema)
-- [Hugo](https://gohugo.io/) (optional, for docs)
-- Go (optional, for docs)
+- [Mintlify](https://mintlify.com/) (optional, for docs)
 - nvm (optional, for managing Node versions)
 
 ## Getting Started
@@ -20,8 +19,8 @@ The following software is required to work on the spec:
 2. Clone your fork:
 
 ```bash
-git clone https://github.com/YOUR-USERNAME/specification.git
-cd specification
+git clone https://github.com/YOUR-USERNAME/modelcontextprotocol.git
+cd modelcontextprotocol
 ```
 
 3. Install dependencies:
@@ -33,8 +32,9 @@ npm install  # install dependencies
 
 ## Making Changes
 
-Note that schema changes are made to `schema.ts`. `schema.json` is generated from
-`schema.ts` using `npm run validate:schema`.
+Note that schema changes are made to `schema.ts`, and `schema.json` is generated from
+`schema.ts`. You should validate your `schema.ts` changes first and then generate the
+`schema.json`.
 
 1. Create a new branch:
 
@@ -47,15 +47,61 @@ git checkout -b feature/your-feature-name
 
 ```bash
 npm run validate:schema    # validate schema
-npm run generate:json     # generate JSON schema
 ```
 
-4. Run docs locally (optional):
+4. Generate the `schema.json`:
+
+```bash
+npm run generate:json      # generate JSON schema
+```
+
+5. Run docs locally (optional):
 
 ```bash
 npm run serve:docs
 ```
 
+6. Format/lint your changes:
+
+```bash
+npm run format:check   # check formatting
+npm run format         # apply formatting
+```
+
+### Documentation Guidelines
+
+When contributing to the documentation:
+
+- Keep content clear, concise, and technically accurate
+- Follow the existing file structure and naming conventions
+- Include code examples where appropriate
+- Use proper MDX formatting and components
+- Test all links and code samples
+  - You may run `npm run check-links` to look for broken internal links.
+- Use appropriate headings: "When to use", "Steps", and "Tips" for tutorials
+- Place new pages in appropriate sections (concepts, tutorials, etc.)
+- Update `docs.json` when adding new pages
+- Follow existing file naming conventions (`kebab-case.mdx`)
+- Include proper frontmatter in MDX files
+
+### Specification Proposal Guidelines
+
+#### Principles of MCP
+
+1. **Simple + Minimal**: It is much easier to add things to a specification than it is to
+   remove them. To maintain simplicity, we keep a high bar for adding new concepts and
+   primitives as each addition requires maintenance and compatibility consideration.
+2. **Concrete**: Specification changes need to be based on specific implementation
+   challenges and not on speculative ideas.
+
+### Stages of a specification proposal
+
+1. **Define**: Explore the problem space, validate that other MCP users face a similar
+   issue, and then clearly define the problem.
+2. **Prototype**: Build an example solution to the problem and demonstrate its practical
+   application.
+3. **Write**: Based on the prototype, write a specification proposal.
+
 ## Submitting Changes
 
 1. Push your changes to your fork

CNAME

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 Anthropic, PBC
+Copyright (c) 2024–2025 Anthropic, PBC and contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

CONTRIBUTING.md

@@ -2,10 +2,13 @@
 
 This repo contains the specification and protocol schema for the Model Context Protocol.
 
-The schema is [defined in TypeScript](schema/2024-11-05/schema.ts) first, but
-[made available as JSON Schema](schema/2024-11-05/schema.json) as well, for wider
+The schema is [defined in TypeScript](schema/2025-03-26/schema.ts) first, but
+[made available as JSON Schema](schema/2025-03-26/schema.json) as well, for wider
 compatibility.
 
+The official MCP documentation is built using Mintlify and available at
+[modelcontextprotocol.io](https://modelcontextprotocol.io).
+
 ## Contributing
 
 Please see [CONTRIBUTING.md](CONTRIBUTING.md) for details on how to contribute to this