Merge branch 'main' into spec/sampling-includecontext

Author: localden

README.md

@@ -1,15 +1,15 @@
 # Model Context Protocol (MCP)
 
-_Just heard of MCP and not sure where to start? See [the documentation website instead](https://modelcontextprotocol.io)._
+_Just heard of MCP and not sure where to start? Check out our [documentation website](https://modelcontextprotocol.io)._
 
 This repo contains the:
 
 - MCP specification
 - MCP protocol schema
 - Official MCP documentation
 
-The schema is [defined in TypeScript](schema/2025-06-18/schema.ts) first, but
-[made available as JSON Schema](schema/2025-06-18/schema.json) as well, for wider
+The schema is [defined in TypeScript](schema/2025-11-25/schema.ts) first, but
+[made available as JSON Schema](schema/2025-11-25/schema.json) as well, for wider
 compatibility.
 
 The official MCP documentation is built using Mintlify and available at

blog/content/_index.md

@@ -1,3 +1,3 @@
 +++
-title = 'blog'
+title = 'Model Context Protocol Blog'
 +++

blog/content/posts/2025-11-25-first-mcp-anniversary.md

@@ -0,0 +1,68 @@
++++
+date = '2025-11-28T11:00:00Z'
+title = 'SEPs Are Moving to Pull Requests'
+author = 'David Soria Parra (Lead Maintainer)'
+tags = ['announcement', 'governance', 'community', 'sep']
++++
+
+We're updating how Specification Enhancement Proposals (SEPs) are submitted and managed. Starting today, SEPs will be created as pull requests to the [`seps/` directory](https://github.com/modelcontextprotocol/modelcontextprotocol/tree/main/seps) instead of GitHub issues.
+
+## Why the Change?
+
+When we [introduced SEPs in July](https://blog.modelcontextprotocol.io/posts/2025-07-31-governance-for-mcp/), we chose GitHub Issues as our starting point. Issues are familiar to developers, low-friction, and got us up and running quickly. But as more proposals have come through the process, we've identified some key pain points:
+
+**Scattered discussions.** With issues, the proposal text lives in the issue body while implementation details often end up in a separate PR. This splits the conversation and makes it harder to follow the full history of a proposal. This also introduces two distinct numbers referencing the same SEP, making it harder to consistently track and manage changes.
+
+**No version history.** Issues don't have the same revision tracking that files in a repository do. When a SEP evolves through review, it's difficult to see what changed and when.
+
+The new PR-based approach, inspired by [Python's PEP process](https://peps.python.org/), solves both problems.
+
+## How It Works
+
+The new workflow will be familiar if you've submitted pull requests on GitHub before:
+
+1. **Draft your SEP** as a markdown file named `0000-your-feature.md` using the [SEP template](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/TEMPLATE.md)
+
+2. **Create a pull request** adding your SEP to the `seps/` directory
+
+3. **Update the SEP number** once your PR is created, rename the file using the PR number (e.g., PR #1850 becomes `1850-your-feature.md`) and push a new commit with the rename
+
+4. **Find a sponsor** from our [maintainer list](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) to shepherd your proposal
+
+5. **Iterate** on feedback directly in the PR
+
+That's it. The PR number becomes the SEP number, discussion happens in one place, and git tracks every revision.
+
+## What About Status?
+
+One notable change: **sponsors are now responsible for updating SEP status**. In addition to applying labels to the pull request, the sponsor is responsible for ensuring that the `Status` field is updated in the SEP markdown file. This keeps the canonical state of the proposal in the file itself, versioned alongside the content, while PR labels make it easy to filter and find SEPs by status.
+
+Status transitions work the same as before: `Draft` to `In-Review` to `Accepted` to `Final`, with the sponsor managing each transition as the proposal progresses.
+
+## Getting Started
+
+Ready to propose a change to MCP? Here's what you need to know:
+
+**For new SEPs:**
+
+- Read the latest [SEP Guidelines](https://modelcontextprotocol.io/community/sep-guidelines)
+- Use the [SEP template](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/README.md#sep-file-structure) to create your proposal
+- Browse existing SEPs in the [`seps/` directory](https://github.com/modelcontextprotocol/modelcontextprotocol/tree/main/seps) for examples
+- Follow the workflow described above
+
+**For existing SEPs:**
+If you have a SEP submitted as a GitHub issue, you can continue with your current workflow. We strongly encourage migrating to the new process for better version control and centralized discussion. To migrate:
+
+1. Create a markdown file using the SEP template, starting with `0000-your-feature.md`
+2. Copy and adapt your proposal content to fit the template structure
+3. Submit a pull request to the `seps/` directory
+4. Rename the file using your new PR number (e.g., PR #1900 becomes `1900-your-feature.md`)
+5. Close the original issue with a link to the new PR
+
+The new PR gets a fresh SEP number and gives your proposal proper version control and centralized discussion. Any valuable context from the original issue discussion should be summarized in the new SEP or referenced via links.
+
+As always, if you're unsure whether your idea warrants a SEP, start a conversation on [Discord](https://modelcontextprotocol.io/community/communication#discord) or [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions). We're happy to help you figure out the right path forward.
+
+## Thank You
+
+This change is a direct result of feedback from contributors who've been through the SEP process. Your input helps us continuously improve how we build MCP together. Keep it coming.

blog/content/posts/2025-11-28-sep-process-update.md

@@ -1,6 +1,7 @@
 baseURL = 'https://blog.modelcontextprotocol.io/'
 languageCode = 'en-us'
-title = 'mcp blog'
+title = 'Model Context Protocol Blog'
+copyright = 'Copyright © 2025 Model Context Protocol Project. All rights reserved.'
 theme = 'github.com/adityatelange/hugo-PaperMod'
 [pagination]
   pagerSize = 5
@@ -9,6 +10,9 @@ theme = 'github.com/adityatelange/hugo-PaperMod'
   author = "The MCP project"
   description = "Updates from the Model Context Protocol project"
 
+  [params.homeInfoParams]
+    Content = "Get the latest updates from protocol maintainers and contributors about new developments, upcoming features, and real-world MCP implementations."
+
   # PaperMod specific settings
   # defaultTheme = "dark" # MCP uses a dark theme
   disableThemeToggle = false
@@ -25,19 +29,19 @@ theme = 'github.com/adityatelange/hugo-PaperMod'
   comments = false
   hidemeta = false
   hideSummary = false
-  showtoc = false
   ShowFullTextinRSS = true
 
-  # Custom copyright
-  copyright = '© 2025 Model Context Protocol Project'
-
   [params.assets]
     favicon = "favicon.svg"
 
   [[params.socialIcons]]
     name = "github"
     url = "https://github.com/modelcontextprotocol"
 
+  [[params.socialIcons]]
+    name = "linkedin"
+    url = "https://linkedin.com/company/modelcontextprotocol"
+
 # Menu configuration
 [[menu.main]]
   identifier = "docs"

blog/hugo.toml

@@ -0,0 +1,136 @@
+{{- if not (.Param "hideFooter") }}
+<footer class="footer">
+    {{- if not site.Params.footer.hideCopyright }}
+        {{- if site.Copyright }}
+        <span>{{ site.Copyright | markdownify }}</span>
+        {{- else }}
+        <span>&copy; {{ now.Year }} <a href="{{ "" | absLangURL }}">{{ site.Title }}</a></span>
+        {{- end }}
+    {{- end }}
+    {{- with site.Params.footer.text }}
+        {{ . | markdownify }}
+    {{- end }}
+</footer>
+{{- end }}
+
+{{- if (not site.Params.disableScrollToTop) }}
+<a href="#top" aria-label="go to top" title="Go to Top (Alt + G)" class="top-link" id="top-link" accesskey="g">
+    <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 12 6" fill="currentColor">
+        <path d="M12 6H0l6-6z" />
+    </svg>
+</a>
+{{- end }}
+
+{{- partial "extend_footer.html" . }}
+
+<script>
+    let menu = document.getElementById('menu');
+    if (menu) {
+        const scrollPosition = localStorage.getItem("menu-scroll-position");
+        if (scrollPosition) {
+            menu.scrollLeft = parseInt(scrollPosition, 10);
+        }
+        
+        menu.onscroll = function () {
+            localStorage.setItem("menu-scroll-position", menu.scrollLeft);
+        }
+    }
+
+    document.querySelectorAll('a[href^="#"]').forEach(anchor => {
+        anchor.addEventListener("click", function (e) {
+            e.preventDefault();
+            var id = this.getAttribute("href").substr(1);
+            if (!window.matchMedia('(prefers-reduced-motion: reduce)').matches) {
+                document.querySelector(`[id='${decodeURIComponent(id)}']`).scrollIntoView({
+                    behavior: "smooth"
+                });
+            } else {
+                document.querySelector(`[id='${decodeURIComponent(id)}']`).scrollIntoView();
+            }
+            if (id === "top") {
+                history.replaceState(null, null, " ");
+            } else {
+                history.pushState(null, null, `#${id}`);
+            }
+        });
+    });
+</script>
+
+{{- if (not site.Params.disableScrollToTop) }}
+<script>
+    var mybutton = document.getElementById("top-link");
+    window.onscroll = function () {
+        if (document.body.scrollTop > 800 || document.documentElement.scrollTop > 800) {
+            mybutton.style.visibility = "visible";
+            mybutton.style.opacity = "1";
+        } else {
+            mybutton.style.visibility = "hidden";
+            mybutton.style.opacity = "0";
+        }
+    };
+</script>
+{{- end }}
+
+{{- if (not site.Params.disableThemeToggle) }}
+<script>
+    document.getElementById("theme-toggle").addEventListener("click", () => {
+        const html = document.querySelector("html");
+        if (html.dataset.theme === "dark") {
+            html.dataset.theme = 'light';
+            localStorage.setItem("pref-theme", 'light');
+        } else {
+            html.dataset.theme = 'dark';
+            localStorage.setItem("pref-theme", 'dark');
+        }
+    })
+</script>
+{{- end }}
+
+{{- if (and (eq .Kind "page") (ne .Layout "archives") (ne .Layout "search") (.Param "ShowCodeCopyButtons")) }}
+<script>
+    document.querySelectorAll('pre > code').forEach((codeblock) => {
+        const container = codeblock.parentNode.parentNode;
+        const copybutton = document.createElement('button');
+        copybutton.classList.add('copy-code');
+        copybutton.innerHTML = '{{- i18n "code_copy" | default "copy" }}';
+
+        function copyingDone() {
+            copybutton.innerHTML = '{{- i18n "code_copied" | default "copied!" }}';
+            setTimeout(() => {
+                copybutton.innerHTML = '{{- i18n "code_copy" | default "copy" }}';
+            }, 2000);
+        }
+
+        copybutton.addEventListener('click', (cb) => {
+            if ('clipboard' in navigator) {
+                navigator.clipboard.writeText(codeblock.textContent);
+                copyingDone();
+                return;
+            }
+
+            const range = document.createRange();
+            range.selectNodeContents(codeblock);
+            const selection = window.getSelection();
+            selection.removeAllRanges();
+            selection.addRange(range);
+            try {
+                document.execCommand('copy');
+                copyingDone();
+            } catch (e) { };
+            selection.removeRange(range);
+        });
+
+        if (container.classList.contains("highlight")) {
+            container.appendChild(copybutton);
+        } else if (container.parentNode.firstChild == container) {
+            // td containing LineNos
+        } else if (codeblock.parentNode.parentNode.parentNode.parentNode.parentNode.nodeName == "TABLE") {
+            // table containing LineNos and code
+            codeblock.parentNode.parentNode.parentNode.parentNode.parentNode.appendChild(copybutton);
+        } else {
+            // code blocks not having highlight as parent class
+            codeblock.parentNode.appendChild(copybutton);
+        }
+    });
+</script>
+{{- end }}