Merge remote-tracking branch 'upstream/main' into add-server-instructions-post-v2

Author: olaservo

.gitignore

@@ -1,2 +1,3 @@
+.claude/
 node_modules/
 .DS_Store

ANTITRUST.md

@@ -0,0 +1,53 @@
+**MCP Project Antitrust Policy**
+
+**Antitrust Policy**
+
+Effective: September 29, 2025
+
+**Introduction**
+
+The goal of the Model Context Protocol open source project (the “Project”) is to develop a universal standard for model-to-world interactions, including enabling LLMs and agents to seamlessly connect with and utilize external data sources and tools. The purpose of this Antitrust Policy (the “Policy”) is to avoid antitrust risks in carrying out this pro-competitive mission.
+
+Participants in and contributors to the Project (collectively, “participants”) will use their best reasonable efforts to comply in all respects with all applicable state and federal antitrust and trade regulation laws, and applicable antitrust/competition laws of other countries (collectively, the “Antitrust Laws”).
+
+The goal of Antitrust Laws is to encourage vigorous competition. Nothing in this Policy prohibits or limits the ability of participants to make, sell or use any product, or otherwise to compete in the marketplace. This Policy provides general guidance on compliance with Antitrust Law. Participants should contact their respective legal counsel to address specific questions.
+
+This Policy is conservative and is intended to promote compliance with the Antitrust Laws, not to create duties or obligations beyond what the Antitrust Laws actually require. In the event of any inconsistency between this Policy and the Antitrust Laws, the Antitrust Laws preempt and control.
+
+**Participation**
+
+Technical participation in the Project shall be open to all, subject only to compliance with the provisions of the Project’s charter and other governance documents.
+
+**Conduct of Meetings**
+
+At meetings among actual or potential competitors, there is a risk that participants in those meetings may improperly disclose or discuss information in violation of the Antitrust Laws or otherwise act in an anti-competitive manner. To avoid this risk, participants must adhere to the following policies when participating in Project-related or sponsored meetings, conference calls, or other forums (collectively, “Project Meetings”).
+
+Participants must not, in fact or appearance, discuss or exchange information regarding:
+
+- An individual company’s current or projected prices, price changes, price differentials, markups, discounts, allowances, terms and conditions of sale, including credit terms, etc., or data that bear on prices, including profits, margins or cost.
+- Industry-wide pricing policies, price levels, price changes, differentials, or the like.
+- Actual or projected changes in industry production, capacity or inventories.
+- Matters relating to bids or intentions to bid for particular products, procedures for responding to bid invitations or specific contractual arrangements.
+- Plans of individual companies concerning the design, characteristics, production, distribution, marketing or introduction dates of particular products, including proposed territories or customers.
+- Matters relating to actual or potential individual suppliers that might have the effect of excluding them from any market or of influencing the business conduct of firms toward such suppliers.
+- Matters relating to actual or potential customers that might have the effect of influencing the business conduct of firms toward such customers.
+- Individual company current or projected cost of procurement, development or manufacture of any product.
+- Individual company market shares for any product or for all products.
+- Confidential or otherwise sensitive business plans or strategy.
+
+In connection with all Project Meetings, participants must do the following:
+
+- Adhere to prepared agendas.
+- Insist that meeting minutes be prepared and distributed to all participants, and that meeting minutes accurately reflect the matters that transpired.
+- Consult with their respective counsel on all antitrust questions related to Project Meetings.
+- Protest against any discussions that appear to violate these policies or the Antitrust Laws, leave any meeting in which such discussions continue, and either insist that such protest be noted in the minutes.
+
+**Requirements/Standard Setting**
+
+The Project may establish standards, technical requirements and/or specifications for use (collectively, “requirements”). Participants shall not enter into agreements that prohibit or restrict any participant from establishing or adopting any other requirements. Participants shall not undertake any efforts, directly or indirectly, to prevent any firm from manufacturing, selling, or supplying any product not conforming to a requirement.
+
+The Project shall not promote standardization of commercial terms, such as terms for license and sale.
+
+**Contact Information**
+
+To contact the Project regarding matters addressed by this Antitrust Policy, please send an email to [email protected], and reference “Antitrust Policy” in the subject line.

CONTRIBUTING.md

@@ -18,37 +18,38 @@ The following software is required to work on the spec:
 ### Getting Started
 
 1. [Fork the repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
+
 2. Clone your fork:
 
-```bash
-git clone https://github.com/YOUR-USERNAME/modelcontextprotocol.git
-cd modelcontextprotocol
-```
+   ```bash
+   git clone https://github.com/YOUR-USERNAME/modelcontextprotocol.git
+   cd modelcontextprotocol
+   ```
 
 3. Install dependencies:
 
-```bash
-nvm install  # install correct Node version
-npm install  # install dependencies
-```
+   ```bash
+   nvm install  # install correct Node version
+   npm install  # install dependencies
+   ```
 
-## Schema changes
+4. Create a new branch:
 
-Note that schema changes are made to `schema.ts`, and `schema.json` is generated from
-`schema.ts`.
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
 
-1. Create a new branch:
+## Schema changes
+
+Schema changes go in `schema/draft/schema.ts`. To validate your changes, run:
 
 ```bash
-git checkout -b feature/your-feature-name
+npm run check:schema:ts
 ```
 
-2. Make your changes.
-
-3. Validate schema changes and generate `schema.json`:
+`schema/draft/schema.json` and `docs/specification/draft/schema.mdx` are generated from `schema/draft/schema.ts`; do not edit them directly. To generate them, run:
 
 ```bash
-npm run check:schema:ts
 npm run generate:schema
 ```
 

MAINTAINERS.md

@@ -1,13 +1,13 @@
 # MCP Maintainers
 
-This document lists current maintainers and working groups in the Model Context Protocol project.
+This document lists current maintainers in the Model Context Protocol project.
 
-**Last updated:** July 23, 2025
+**Last updated:** October 15, 2025
 
 ## Lead Maintainers
 
-- [Justin Spahr-Summers](https://github.com/jspahrsummers)
 - [David Soria Parra](https://github.com/dsp-ant)
+- _[Justin Spahr-Summers](https://github.com/jspahrsummers) (currently inactive)_
 
 ## Core Maintainers
 
@@ -41,6 +41,8 @@ This document lists current maintainers and working groups in the Model Context
 ### Go SDK
 
 - [Rob Findley](https://github.com/findleyr)
+- [Jonathan Amsterdam](https://github.com/jba)
+- [Sam Thanawalla](https://github.com/samthanawalla)
 
 ### C# SDK
 
@@ -69,6 +71,11 @@ This document lists current maintainers and working groups in the Model Context
 
 - [Alex Hancock](https://github.com/alexhancock)
 
+### PHP SDK
+
+- [Kyrian Obikwelu](https://github.com/CodeWithKyrian)
+- [Christopher Hertel](https://github.com/chr-hertel)
+
 ## Project Maintainers
 
 ### use-mcp
@@ -85,6 +92,7 @@ This document lists current maintainers and working groups in the Model Context
 - [Toby Padilla](https://github.com/toby)
 - [Tadas Antanavicius](https://github.com/tadasant)
 - [Adam Jones](https://github.com/domdomegg)
+- [Radoslav (Rado) Dimitrov](https://github.com/rdimitrov)
 
 ### Reference Servers
 
@@ -102,33 +110,55 @@ This document lists current maintainers and working groups in the Model Context
 - [Jonathan Hefner](https://github.com/jonathanhefner)
 - [Tadas Antanavicius](https://github.com/tadasant)
 
-## Working Groups
+## Working Group & Interest Group Maintainers
+
+[Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups) are not required to have maintainers (they can be managed by informal facilitators), but maintainers may be appointed on an as-needed basis.
 
-### Security Working Group
+### Security Interest Group
 
 - [Den Delimarsky](https://github.com/dend)
 - [Paul Carleton](https://github.com/pcarleton)
 - [Jenn Newton](https://github.com/jenn-newton)
 
-### Authorization Working Group
+### Authorization Interest Group
 
 - [Aaron Parecki](https://github.com/aaronpk)
 - [Darin McAdams](https://github.com/D-McAdams)
 - [Paul Carleton](https://github.com/pcarleton)
 
-### Client Implementor Working Group
+### Client Implementor Interest Group
+
+**Note:** These individuals serve as MCP protocol representatives for their respective clients. For client-specific issues, use the official support channels provided by each product.
+
+- [Alex Hancock](https://github.com/alexhancock) - Goose
+- [Ben Brandt](https://github.com/benbrandt) - Zed
+- [Connor Peet](https://github.com/connor4312) - VS Code
+- [Gabriel Peal](https://github.com/gpeal) - Codex
+- [Jun Han](https://github.com/formulahendry) - GitHub Copilot for JetBrains
+- [Tyler Leonhardt](https://github.com/TylerLeonhardt) - VS Code
+- [Michael Feldstein](https://github.com/msfeldstein) - Cursor
+
+### Financial Services Interest Group
 
-- [Michael Feldstein](https://github.com/msfeldstein)
-- [Harald Kirschner](https://github.com/digitarald)
-- [Connor Peet](https://github.com/connor4312)
+- [Sambhav Kothari](https://github.com/sambhav)
 
-### Transports Working Group
+### Transports Interest Group
 
 - [Kurtis Van Gent](https://github.com/kurtisvg)
 - [Jonathan Hefner](https://github.com/jonathanhefner)
 - [Shaun Smith](https://github.com/evalstate)
 - [Harvey Tuch](https://github.com/htuch)
 
+### Server Identity Working Group
+
+- [Nick Cooper](https://github.com/nicknotfun)
+
+### Agents Working Group
+
+- [Peter Alexander](https://github.com/pja-ant)
+- [Luca Chang](https://github.com/LucaButBoring)
+- [Inna Harper](https://github.com/ihrpr)
+
 ## About This Document
 
 This document is updated by the MCP maintainers and reflects the current

README.md

@@ -15,6 +15,10 @@ compatibility.
 The official MCP documentation is built using Mintlify and available at
 [modelcontextprotocol.io](https://modelcontextprotocol.io).
 
+## Authors
+
+The Model Context Protocol was created by David Soria Parra ([@dsp](https://github.com/dsp)) and Justin Spahr-Summers ([@jspahrsummers](https://github.com/jspahrsummers)).
+
 ## Contributing
 
 See [CONTRIBUTING.md](./CONTRIBUTING.md).

blog/content/posts/2025-09-26-mcp-next-version-update.md

@@ -0,0 +1,109 @@
+---
+title: "Update on the Next MCP Protocol Release"
+date: 2025-09-26T10:00:00-08:00
+draft: false
+tags: ["mcp", "protocol", "roadmap", "community"]
+author: "David Soria Parra"
+description: "An update on the timeline and priorities for the next Model Context Protocol specification version"
+---
+
+## Release Timeline
+
+The next version of the Model Context Protocol specification will be released on **November 25th, 2025**, with a release candidate (RC) available on **November 11th, 2025**.
+
+We're building in a 14-day RC validation window so client implementors and SDK maintainers can thoroughly test the protocol changes. This approach gives us the focused time we need to deliver critical improvements while applying our [new governance model](https://modelcontextprotocol.io/community/governance) to the process.
+
+## Summer Progress
+
+Our last spec was released on June 18, 2025, and focused on structured tool outputs, OAuth-based authorization, elicitation for server-initiated user interactions, and improved security best practices.
+
+Since then, we’ve focused on establishing additional foundations for the MCP ecosystem:
+
+### Formal Governance Structures
+
+We established a [formal governance model for MCP](https://modelcontextprotocol.io/community/governance), including defined roles and decision-making mechanisms. We also developed the [Specification Enhancement Proposal (SEP)](https://modelcontextprotocol.io/community/sep-guidelines) process to provide clear guidelines for contributing specification changes.
+
+Our goal is transparency—making decision-making procedures clear and accessible to everyone. Like any new system serving a fast-evolving community, our governance model is still finding its footing. We're actively refining it as both the protocol and community continue to grow.
+
+### Working Groups
+
+We've launched [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups) to foster community collaboration. These groups serve multiple purposes:
+
+- Provide clear entry points for new contributors
+- Empower community members to lead initiatives in their areas of expertise
+- Distribute ownership across the ecosystem rather than concentrating it among core maintainers
+
+We're developing governance structures that will grant these groups greater autonomy in decision-making and implementation. This distributed approach ensures the protocol can grow to meet community needs while maintaining quality and consistency across different domains.
+
+### Registry Development
+
+In September, we [launched the MCP Registry preview](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)—an open catalog and API for indexing and discovery of MCP servers. The Registry serves as the single source of truth for available MCP servers, supporting both public and private sub-registries that organizations can customize for their specific needs.
+
+Building the MCP Registry has been a true community effort. Any MCP client can consume registry content via the native API or through third-party registry aggregators, making it easier for users to discover and integrate MCP servers into their AI workflows.
+
+## Priority Areas for the Next Release
+
+With governance and infrastructure foundations in place, we're focusing on five key protocol improvements identified by our working groups.
+
+### Asynchronous Operations
+
+Currently, MCP is built around mostly synchronous operations—when you call a tool, everything stops and waits for it to finish. That works great for quick tasks, but what about operations that take minutes or hours?
+
+The Agents Working Group is adding async support, allowing servers to kick off long-running tasks while clients can check back later for results. You can follow the progress in [SEP-1391](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1391).
+
+### Statelessness and Scalability
+
+As organizations deploy MCP servers at enterprise scale, we're seeing new requirements emerge. Current implementations often need to remember things between requests, which makes horizontal scaling across multiple server instances challenging.
+
+While [Streamable HTTP](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http) provides some stateless support, pain points remain around server startup and session handling. The Transport Working Group is smoothing out these rough edges, making it easier to run MCP servers in production while keeping simple upgrade paths for teams who want more sophisticated stateful features.
+
+### Server Identity
+
+Today, if you want to know what an MCP server can do, you have to connect to it first. This makes it difficult for clients to browse available servers or for systems like our registry to automatically catalog capabilities.
+
+We're solving this by letting servers advertise themselves through [`.well-known` URLs](https://en.wikipedia.org/wiki/Well-known_URI)—an established standard for providing metadata. Think of it as a server's business card that anyone can read without having to knock on the door first. This will make discovery much more intuitive for every MCP consumer.
+
+### Official Extensions
+
+As MCP has grown, we've noticed patterns emerging for specific industries and use cases—valuable implementations that don't necessarily belong in the core protocol specification.
+
+Rather than leaving everyone to reinvent the wheel, we're officially recognizing and documenting the most popular protocol extensions. This curated collection of proven patterns will give developers building for specialized domains like healthcare, finance, or education a solid starting point instead of building every custom integration from scratch.
+
+### SDK Support Standardization
+
+Choosing an MCP SDK today can be challenging—it's hard to gauge the level of support or spec compliance you'll get. Some SDKs are lightning-fast with updates, while others might lag behind feature-wise.
+
+We're introducing a clear tiering system for SDKs. You'll know exactly what you're signing up for before committing to a dependency, based on factors like specification compliance speed, maintenance responsiveness, and feature completeness.
+
+## Call for Contributors
+
+MCP is only as strong as the community behind it. Whether you're an individual developer passionate about building SDKs or a company looking to invest in the ecosystem, we need your help in several key areas.
+
+### SDK Maintenance
+
+- [**TypeScript SDK**](https://github.com/modelcontextprotocol/typescript-sdk) - Needs additional maintainers for feature development and bug fixes
+- [**Swift SDK**](https://github.com/modelcontextprotocol/swift-sdk) - Requires attention for Apple ecosystem support
+- [Other language SDKs](https://modelcontextprotocol.io/docs/sdk) welcome continued contributions
+
+### Tooling
+
+- [**Inspector**](https://github.com/modelcontextprotocol/inspector) - Development and maintenance of debugging tools for MCP server developers
+- [**Registry**](https://github.com/modelcontextprotocol/registry) - Backend API and CLI development; **Go expertise would be particularly welcome**
+
+## Input from Client Developers
+
+We talk a lot about MCP servers, but clients are equally important—they're the bridge connecting users to the entire MCP ecosystem. If you're building an MCP client, you're seeing the protocol from a unique angle, and we need that perspective embedded in the protocol design.
+
+Your real-world experience with implementation challenges, performance bottlenecks, and user needs directly shapes where the protocol should go next. Whether it's feedback on existing capabilities or ideas for streamlining the developer experience, we want to hear from you.
+
+Join us in the `#client-implementors` working group channel in the [MCP Discord](https://modelcontextprotocol.io/community/communication).
+
+## Looking Ahead
+
+With governance structures and working groups in place, we're better positioned to tackle major protocol improvements efficiently while ensuring everyone has a voice in the process. The foundational work we've done this summer gives us a solid base to build from.
+
+The improvements coming in November—async operations, better scalability, server discovery, and standardized extensions—will help MCP become a stronger backbone for production AI integrations. But we can't do it alone.
+
+MCP's strength has always been that it's an **open protocol built by the community, for the community**. We're excited to keep building it together.
+
+Thank you for your continued support, and we look forward to sharing more soon.