[blog] Governance for MCP (modelcontextprotocol#989)

* Add blog link to documentation navbar

Added blog.modelcontextprotocol.io to the navbar links to provide easy access to the MCP blog from the documentation site.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* package.json: and a script to serve the blog

* blog: Add a blog entry about the governance for MCP

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Aaron Parecki <[email protected]>

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Tadas Antanavicius <[email protected]>

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Jonathan Hefner <[email protected]>

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Jonathan Hefner <[email protected]>

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Tadas Antanavicius <[email protected]>

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Den Delimarsky 🌺 <[email protected]>

* Update blog/content/posts/2025-07-17-governance-for-mcp.md

Co-authored-by: Den Delimarsky 🌺 <[email protected]>

* npm run format

---------

Co-authored-by: Claude <[email protected]>
Co-authored-by: Aaron Parecki <[email protected]>
Co-authored-by: Tadas Antanavicius <[email protected]>
Co-authored-by: Jonathan Hefner <[email protected]>
Co-authored-by: Den Delimarsky 🌺 <[email protected]>

Author: 6 people

blog/content/posts/2025-07-17-governance-for-mcp.md

@@ -0,0 +1,47 @@
++++
+date = '2025-07-17T10:00:00Z'
+draft = true
+title = 'Governance for MCP'
+author = 'David Soria Parra (Lead Maintainer)'
+tags = ['announcement', 'governance', 'community']
++++
+
+The Model Context Protocol project has adopted a formal [governance structure](https://modelcontextprotocol.io/community/governance) to guide its development.
+
+Since MCP's open source release in November 2024, the project has grown rapidly. Our informal processes haven't scaled with this growth, leading to unclear decision-making and stale pull requests. Today we're addressing these challenges with a formal governance model.
+
+## Governance Structure
+
+The new model establishes three tiers of leadership:
+
+- **Maintainers** manage specific components (SDKs, documentation, repositories)
+- **Core Maintainers** guide overall project direction and specification evolution
+- **Lead Maintainers** serve as final decision-makers with veto power
+
+All maintainers form the MCP steering group. Core and lead maintainers meet bi-weekly to review [Specification Enhancement Proposals (SEPs)](#specification-enhancement-proposals-seps). Meeting notes and decisions from these meetings will be made public, ensuring transparent governance for the entire community.
+
+## Specification Enhancement Proposals (SEPs)
+
+We're introducing the [Spec Enhancement Proposal](https://modelcontextprotocol.io/community/sep-guidelines) (SEP) as the primary mechanism for proposing changes to MCP, similar to Python's PEPs or Rust's RFCs. Briefly, the SEP process is:
+
+1. Submit a proposal as a GitHub issue
+2. Find a steering group sponsor through the [MCP Discord](https://discord.gg/modelcontextprotocol) or GitHub
+3. Progress through draft, review, and implementation stages
+
+SEPs ensure thoughtful evolution of the protocol while maintaining an open contribution process.
+
+## Get Involved
+
+We're actively looking for contributors at all levels:
+
+- **New Contributors**: Start with documentation improvements, bug fixes, or examples. Every contribution matters, and we're here to help you get started.
+
+- **SDK Developers**: Help build or maintain SDKs in new languages. We especially need maintainers for emerging language ecosystems.
+
+- **Documentation Writers**: Clear documentation is crucial for MCP's success. Help us improve guides, tutorials, and API references.
+
+- **Future Maintainers**: Show your expertise through consistent contributions. We promote from within our community based on merit and commitment.
+
+Join our [Discord](https://discord.gg/modelcontextprotocol) to connect with other contributors, ask questions, and find mentorship. Whether you're fixing typos or proposing protocol changes through SEPs, there's a place for you in the MCP community.
+
+For details, see our [governance documentation](https://modelcontextprotocol.io/community/governance).

docs/docs.json

@@ -10,6 +10,10 @@
   "favicon": "/favicon.svg",
   "navbar": {
     "links": [
+      {
+        "label": "Blog",
+        "href": "https://blog.modelcontextprotocol.io"
+      },
       {
         "label": "GitHub",
         "href": "https://github.com/modelcontextprotocol"

package.json

@@ -33,7 +33,8 @@
     "generate:schema:json": "for f in schema/*/schema.ts; do typescript-json-schema --defaultNumberType integer --required --skipLibCheck \"$f\" \"*\" -o \"${f%.ts}.json\"; done",
     "generate:schema:md": "for f in docs/specification/*/schema.mdx; do typedoc --entryPoints \"schema/$(basename -- $(dirname -- \"$f\"))/schema.ts\" > \"$f\"; done",
     "format": "prettier --write \"**/*.{md,mdx}\" --ignore \"docs/specification/*/schema.mdx\" ",
-    "serve:docs": "cd docs && mintlify dev"
+    "serve:docs": "cd docs && mintlify dev",
+    "serve:blog": "cd blog && hugo serve"
   },
   "devDependencies": {
     "ajv": "^8.17.1",