Merge branch 'main' into feat/user-agent

Author: LucaButBoring

.github/CODEOWNERS

@@ -8,5 +8,5 @@
 /schema/ @modelcontextprotocol/core-maintainers
 
 # Authorization-related files - @auth team should be notified
-/docs/specification/**/authorization.mdx @modelcontextprotocol/core-maintainers @modelcontextprotocol/auth
-/docs/specification/**/security_best_practices.mdx @modelcontextprotocol/core-maintainers @modelcontextprotocol/auth
+/docs/specification/**/authorization.mdx @modelcontextprotocol/core-maintainers @modelcontextprotocol/auth-wg
+/docs/specification/**/security_best_practices.mdx @modelcontextprotocol/core-maintainers @modelcontextprotocol/auth-wg

.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:
+
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
 
-Note that schema changes are made to `schema.ts`, and `schema.json` is generated from
-`schema.ts`.
+## Schema changes
 
-1. Create a new branch:
+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
 ```
 
@@ -69,7 +70,17 @@ npm run check:docs
 npm run format
 ```
 
-### Documentation Guidelines
+## Blog changes
+
+The blog is built using [Hugo](https://gohugo.io/installation/) and located in the [`blog`](./blog) directory.
+
+To preview blog changes locally:
+
+```bash
+npm run serve:blog
+```
+
+## Documentation Guidelines
 
 When contributing to the documentation:
 
@@ -85,9 +96,9 @@ When contributing to the documentation:
 - Follow existing file naming conventions (`kebab-case.mdx`)
 - Include proper frontmatter in MDX files
 
-### Specification Proposal Guidelines
+## Specification Proposal Guidelines
 
-#### Principles of MCP
+### 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

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
 
@@ -25,6 +25,7 @@ This document lists current maintainers and working groups in the Model Context
 
 - [Christian Tzolov](https://github.com/tzolov)
 - [Dariusz Jędrzejczyk](https://github.com/chemicL)
+- [Daniel Garnier-Moiroux](https://github.com/Kehrlann)
 
 ### Ruby SDK
 
@@ -40,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
 
@@ -68,16 +71,36 @@ 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
 
-- [Glen Maddern](https://github.com/geelen) (use-mcp)
-- [Ola Hungerford](https://github.com/olaservo) (Inspector, Reference Servers)
-- [Cliff Hall](https://github.com/cliffhall) (Inspector, Reference Servers)
-- [Toby Padilla](https://github.com/toby) (Registry)
-- [Tadas Antanavicius](https://github.com/tadasant) (Registry, Reference Servers)
-- [Shaun Smith](https://github.com/evalstate) (Reference Servers)
-- [Jonathan Hefner](https://github.com/jonathanhefner) (Reference Servers)
-- [Adam Jones](https://github.com/domdomegg) (Registry)
+### use-mcp
+
+- [Glen Maddern](https://github.com/geelen)
+
+### Inspector
+
+- [Ola Hungerford](https://github.com/olaservo)
+- [Cliff Hall](https://github.com/cliffhall)
+
+### Registry
+
+- [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
+
+- [Ola Hungerford](https://github.com/olaservo)
+- [Cliff Hall](https://github.com/cliffhall)
+- [Tadas Antanavicius](https://github.com/tadasant)
+- [Shaun Smith](https://github.com/evalstate)
+- [Jonathan Hefner](https://github.com/jonathanhefner)
 
 ## Community Moderators
 
@@ -87,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/assets/css/extended/custom.css

@@ -6,4 +6,14 @@
 /* Dark mode remains unchanged */
 .dark.list {
     background: var(--theme);
-}
+}
+
+/* Mermaid diagram styling for dark mode */
+.dark .mermaid {
+    filter: invert(0.85) hue-rotate(180deg);
+}
+
+/* Prevent awkward wrapping in post metadata. See https://github.com/adityatelange/hugo-PaperMod/issues/1789 */
+.post-meta {
+    display: block !important;
+}

blog/content/posts/2025-09-05-php-sdk.md

@@ -0,0 +1,29 @@
++++
+date = '2025-09-05T00:00:00Z'
+title = 'Announcing the Official PHP SDK for MCP'
+author = 'David Soria Parra (Lead Maintainer), Christopher Hertel (Symfony), Roman Pronskiy (PHP Foundation)'
+tags = ['announcement', 'community']
++++
+
+The official [PHP SDK](https://github.com/modelcontextprotocol/php-sdk) for the Model Context Protocol is now generally available.
+
+Built in collaboration with the [PHP Foundation](https://thephp.foundation/) and [Symfony](https://symfony.com/), the PHP SDK handles protocol details, so developers don’t have to worry about low-level mechanics and can focus on building their applications.
+
+The initial release enables PHP developers to build MCP [servers](https://modelcontextprotocol.io/docs/learn/server-concepts), exposing [tools](https://modelcontextprotocol.io/docs/learn/server-concepts#tools-ai-actions), [prompts](https://modelcontextprotocol.io/docs/learn/server-concepts#prompts-interaction-templates), and [resources](https://modelcontextprotocol.io/docs/learn/server-concepts#resources-context-data) to AI applications. Support for PHP applications to act as MCP [clients](https://modelcontextprotocol.io/docs/learn/client-concepts) will follow.
+
+The PHP SDK now joins 9 other [officially supported language SDKs](https://modelcontextprotocol.io/docs/sdk) in the MCP ecosystem, making it easier for developers everywhere to adopt MCP in their preferred language.
+
+## Get involved
+
+The PHP SDK is now open to the community to install, test, and contribute:
+
+- SDK repo: [modelcontextprotocol/php-sdk](https://github.com/modelcontextprotocol/php-sdk)
+- Composer package: [mcp/sdk](https://packagist.org/packages/mcp/sdk)
+
+We welcome your feedback and contribution, including issues, documentation improvements, and pull requests. Framework-specific integrations and real-world examples are also particularly valuable.
+
+## Thanks to the MCP community
+
+This release consolidates earlier community work into a single, trusted implementation. The SDK is maintained by the [Symfony](https://symfony.com/) team, with [Kyrian Obikwelu](https://github.com/CodeWithKyrian) joining as a maintainer based on his previous [PHP-MCP](https://github.com/php-mcp) work. The [PHP Foundation](https://thephp.foundation/) helped to coordinate the initiative with support from the members of MCP steering group.
+
+Thank you to all involved in bringing PHP to the MCP ecosystem.