Merge branch 'main' into patch-4

localden · web-flow · commit f00ec279e0b8 · 2025-07-31T16:54:15.000-07:00
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
@@ -15,7 +15,7 @@ This document lists current maintainers and working groups in the Model Context
 - [Basil Hosmer](https://github.com/bhosmer-ant)
 - [Paul Carleton](https://github.com/pcarleton)
 - [Nick Cooper](https://github.com/nicknotfun)
-- Nick Aldridge
+- [Nick Aldridge](https://github.com/000-000-000-000-000)
 - Che Liu
 - [Den Delimarsky](https://github.com/localden)
 
diff --git a/blog/content/posts/2025-07-17-governance-for-mcp.md b/blog/content/posts/2025-07-17-governance-for-mcp.md
diff --git a/blog/content/posts/2025-07-31-governance-for-mcp.md b/blog/content/posts/2025-07-31-governance-for-mcp.md
@@ -0,0 +1,53 @@
++++
+date = '2025-07-31T00:00:00Z'
+title = 'Building to Last: A New Governance Model for MCP'
+author = 'David Soria Parra (Lead Maintainer)'
+tags = ['announcement', 'governance', 'community']
++++
+
+Since its open source release in November of 2024, the Model Context Protocol project has grown faster than we could have ever imagined. That's a wonderful problem to have, but with growth come growing pains. Our existing processes, which worked well for a small team, have started to show their limits.
+
+Today, we're taking a big step to ensure MCP can continue to grow and thrive. We're introducing a formal governance model designed to bring clarity to the development process while preserving the collaborative, open source spirit that has made MCP successful.
+
+## Specification Enhancement Proposals (SEPs)
+
+One of the first major changes we're introducing is [Specification Enhancement Proposals](https://modelcontextprotocol.io/community/sep-guidelines) (SEPs). This will be the primary mechanism for anyone to propose changes to MCP. SEPs are inspired by other projects, like [Python PEPs](https://peps.python.org/) or [Rust RFCs](https://github.com/rust-lang/rfcs). We aim to make the process for suggesting changes to Model Context Protocol as straightforward as possible:
+
+1. Following the [SEP guidelines](https://modelcontextprotocol.io/community/sep-guidelines), submit a proposal as [a GitHub issue](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) to start the conversation.
+2. Our maintainers and core maintainers regularly review proposals and tag SEPs for review and sponsorship. You can also reach out and collaborate with contributing folks on [Discord](https://discord.gg/6CSzBmMkjX) or [GitHub](https://github.com/modelcontextprotocol/modelcontextprotocol). Refer to [`MAINTAINERS.md`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) for a list of currently active maintainers and their focus areas.
+3. Work with the sponsor and the MCP community to move your proposal through draft, review, and implementation stages.
+
+SEPs provide a clear, documented path for evolving the protocol, ensuring that every major change is well-vetted by the community.
+
+## Leadership Roles
+
+The new model also establishes three types of leadership roles, ensuring both focused ownership and broad community representation:
+
+- **Maintainers** manage specific components like SDKs, our documentation, and individual repositories.
+- **Core Maintainers** guide the overall direction of the project and the evolution of the MCP specification.
+- **Lead Maintainers** serve as the final decision-makers and ensure the project's long-term health.
+
+All maintainers form the **MCP steering group**. To ensure a structured and timely review of incoming proposals, our core and lead maintainers will meet bi-weekly to review submitted [SEPs](#specification-enhancement-proposals-seps). Meeting notes and decisions will always be public. For example the [notes from the core maintainer meeting on July 23rd, 2025](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1061).
+
+## Get Involved
+
+We need your help to build the future of MCP, and everyone is welcome here. Whether you're a seasoned open source veteran or just curious about how to get started, there's a place for you in our community.
+
+Many of our maintainers began with a single small contribution—sometimes just fixing a typo or asking a thoughtful question. Every journey starts somewhere, and we're excited to help you take your first step.
+
+- **New Contributors**: Unsure where to begin? Start by helping with documentation, fixing bugs, or building out examples. Every contribution matters, and we're here to support you. Check out issues tagged with [`good first issue`](https://github.com/modelcontextprotocol/modelcontextprotocol/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22) - they're perfect for getting started, and you'll find friendly faces ready to help.
+- **SDK Developers**: Have a favorite programming language? As MCP grows, we need your expertise to build and maintain the protocol SDKs. Your work could empower entire new communities to use MCP.
+- **Documentation Writers**: Clear, comprehensive [documentation](https://modelcontextprotocol.io/introduction) is what turns a good project into a great one. If you love explaining things or making guides, your contributions will help others succeed.
+- **Future Maintainers**: We believe in growing our team from within. The path to becoming a maintainer starts with consistent, quality contributions and a commitment to the project's success. Imagine yourself guiding new contributors and shaping the future of MCP.
+
+No matter your background or experience, you belong here. Join our [Discord](https://discord.gg/6CSzBmMkjX) to connect with other contributors, ask questions, and find mentorship. Whether you're fixing a typo or proposing a major change to the protocol, your voice is valued and your efforts make a difference.
+
+For all the details, please see our full [governance documentation](https://modelcontextprotocol.io/community/governance).
+
+## Thank You
+
+None of this would be possible without the incredible community that has rallied around MCP. From the early adopters who believed in the vision, to the developers building MCP clients and servers, to the maintainers dedicating their time and expertise. Every contribution has been essential to making the Model Context Protocol the success it is today.
+
+You've helped us identify issues, improve documentation, build SDKs, create compelling examples, and push the boundaries of what's possible with platform integration. Your feedback, bug reports, feature requests, and code contributions have shaped MCP into something far better than we could have built alone.
+
+As we embark on this next chapter with formal governance, we're more committed than ever to fostering the open, inclusive community that has made MCP thrive. Thank you for being part of this journey - we can't wait to see what we'll build together next.
diff --git a/docs/clients.mdx b/docs/clients.mdx
@@ -41,7 +41,7 @@ This page provides an overview of applications that support the Model Context Pr
 | [FLUJO][FLUJO]                                   | ❌          | ❌        | ✅      | ❓                     | ❌         | ❌    | ❓            |
 | [Genkit][Genkit]                                 | ⚠️          | ✅        | ✅      | ❓                     | ❌         | ❌    | ❓            |
 | [Glama][Glama]                                   | ✅          | ✅        | ✅      | ❓                     | ❌         | ❌    | ❓            |
-| [Gemini CLI][Gemini CLI]                         | ❌          | ❌        | ✅      | ❓                     | ❌         | ❌    | ❓            |
+| [Gemini CLI][Gemini CLI]                         | ❌          | ✅        | ✅      | ❓                     | ❌         | ❌    | ❓            |
 | [GenAIScript][GenAIScript]                       | ❌          | ❌        | ✅      | ❓                     | ❌         | ❌    | ❓            |
 | [GitHub Copilot coding agent][GitHubCopilotCodingAgent]                       | ❌          | ❌        | ✅      | ❌                     | ❌         | ❌    | ❌            |
 | [Goose][Goose]                                   | ✅          | ✅        | ✅      | ❓                     | ❌         | ❌    | ❓            |
diff --git a/docs/community/communication.mdx b/docs/community/communication.mdx
@@ -0,0 +1,98 @@
+---
+title: Contributor Communication
+description: Communication strategy and framework for the Model Context Protocol community
+---
+
+This document provides practical guidance for communicating and collaborating within the Model Context Protocol (MCP) project. It outlines the communication channels, workflows, and processes used by the MCP community.
+
+All communication within the MCP community is governed by our [Code of Conduct](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CODE_OF_CONDUCT.md). We expect all participants to maintain respectful, professional, and inclusive interactions across all channels.
+
+## Communication Channels
+
+We support three primary communication channels: the public Discord server, [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues), and [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) in the [main project repository](https://github.com/modelcontextprotocol/modelcontextprotocol).
+
+### Discord
+
+For real-time contributor discussion and collaboration. The server is designed around **MCP contributors** and is not intended
+to be a place for general MCP support.
+
+The Discord server will have both public and private channels.
+
+#### Public Channels (Default)
+
+- **Purpose**: Open community engagement, collaborative development, and transparent project coordination.
+- Primary use cases:
+  - **Public SDK and tooling development**: All development, from ideation to release planning, happens in public channels (e.g., `#typescript-sdk-dev`, `#inspector-dev`).
+  - **Working and interest group discussions** (`#client-implementors`, `#agents-wg`, etc.)
+    - **Working Group**: Some specific goal or project in mind (such as an SDK, inspector, registry, server-identity, load-balancing, etc).
+    - **Interest Group**: An abstract gathering of folks that might raise a range of various topics. Some might get actioned on as one-offs, others might spin into Working Groups.
+  - **Community onboarding** and contribution guidance.
+  - **Community feedback** and collaborative brainstorming.
+  - Public **office hours** and **maintainer availability**.
+- Avoid:
+  - MCP user support: participants are expected to read official documentation and start new GitHub Discussions for questions or support.
+  - Service or product marketing: interactions on this Discord are expected to be vendor-neutral and not used for brand-building or sales. Mentions of brands or products are discouraged outside of being used as examples or responses to conversations that start off focused on the specification.
+
+#### Private channels (Exceptions)
+
+- **Purpose**: Confidential coordination and sensitive matters that cannot be discussed publicly. Access will be restricted to designated maintainers.
+- **Strict criteria for private use**:
+  - **Security incidents** (CVEs, protocol vulnerabilities).
+  - **People matters** (maintainer-related discussions, code of conduct policies).
+  - Select channels will be configured to be **read-only**. This can be good for example for maintainer decision making.
+  - Coordination requiring **immediate** or otherwise **focused response** with a limited audience.
+- **Transparency**:
+  - **All technical and governance decisions** affecting the community **must be documented** in GitHub Discussions and/or Issues, and will be labeled with `notes`.
+  - **Some matters related to individual contributors** may remain private when appropriate (e.g., personal circumstances, disciplinary actions, or other sensitive individual matters).
+  - Private channels are to be used as **temporary "incident rooms,"** not for routine development.
+
+Any significant discussion on Discord that leads to a potential decision or proposal must be moved to a GitHub Discussion or GitHub Issue to create a persistent, searchable record. Proposals will then be promoted to full-fledged PRs with associated work items (GitHub Issues) as needed.
+
+### GitHub Discussions
+
+For structured, long-form discussion and debate on project direction, features, improvements, and community topics.
+
+When to use:
+
+- Project roadmap planning and milestone discussions
+- Announcements and release communications
+- Community polls and consensus-building processes
+- Feature requests with context and rationale
+  - If a particular repository does not have GitHub Discussions enabled, feel free to open a GitHub Issue instead.
+
+### GitHub Issues
+
+For bug reports, feature tracking, and actionable development tasks.
+
+When to use:
+
+- Submit SEP proposals (following the [SEP guidelines](./sep-guidelines))
+- Bug reports with reproducible steps
+- Documentation improvements with specific scope
+- CI/CD problems and infrastructure issues
+- Release tasks and milestone tracking
+
+### Security Issues
+
+**Do not post security issues publicly.** Instead:
+
+1. Use the private security reporting process. For protocol-level security issues, follow the process in [SECURITY.md in the modelcontextprotocol GitHub repository](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/SECURITY.md).
+2. Contact lead and/or [core maintainers](./governance#current-core-maintainers) directly.
+3. Follow responsible disclosure guidelines.
+
+## Decision Records
+
+All MCP decisions are documented and captured in public channels.
+
+- **Technical decisions**: [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) and SEPs.
+- **Specification changes**: [On the Model Context Protocol website](https://modelcontextprotocol.io/specification/draft/changelog).
+- **Process changes**: [Community documentation](https://modelcontextprotocol.io/community/governance).
+- **Governance decisions and updates**: [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) and SEPs.
+
+When documenting decisions, we will retain as much context as possible:
+
+- Decision makers
+- Background context and motivation
+- Options that were considered
+- Rationale for the chosen approach
+- Implementation steps
diff --git a/docs/docs.json b/docs/docs.json
@@ -281,6 +281,7 @@
         "pages": [
           "community/governance",
           "community/sep-guidelines",
+          "community/communication",
           "development/roadmap",
           "development/contributing",
           "clients",
