From c8bfb1473e6a409b830442f64411bc65b610fa3a Mon Sep 17 00:00:00 2001 From: Justin Spahr-Summers Date: Tue, 17 Dec 2024 15:26:20 +0000 Subject: [PATCH 1/5] Add Development > Contributing page --- development/contributing.mdx | 10 ++++++++++ introduction.mdx | 2 +- mint.json | 13 ++++++++++++- 3 files changed, 23 insertions(+), 2 deletions(-) create mode 100644 development/contributing.mdx diff --git a/development/contributing.mdx b/development/contributing.mdx new file mode 100644 index 0000000..52fb1f3 --- /dev/null +++ b/development/contributing.mdx @@ -0,0 +1,10 @@ +--- +title: Contributing +description: How to participate in Model Context Protocol development +--- + +We welcome contributions from the community! Please review our [contributing guidelines](https://github.com/modelcontextprotocol/.github/blob/main/CONTRIBUTING.md) for details on how to submit changes. + +All contributors must adhere to our [Code of Conduct](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md). + +For questions and discussions, please use [GitHub Discussions](https://github.com/orgs/modelcontextprotocol/discussions). diff --git a/introduction.mdx b/introduction.mdx index 86e692c..6e3f935 100644 --- a/introduction.mdx +++ b/introduction.mdx @@ -151,4 +151,4 @@ Dive deeper into MCP's core concepts and capabilities: ## Contributing -Want to contribute? Check out [@modelcontextprotocol](https://github.com/modelcontextprotocol) on GitHub to join our growing community of developers building with MCP. \ No newline at end of file +Want to contribute? Check out our [Contributing Guide](/development/contributing) to learn how you can help improve MCP. \ No newline at end of file diff --git a/mint.json b/mint.json index f5e0382..ffbf4fa 100644 --- a/mint.json +++ b/mint.json @@ -40,7 +40,12 @@ "navigation": [ { "group": "Get Started", - "pages": ["introduction", "quickstart", "examples", "clients"] + "pages": [ + "introduction", + "quickstart", + "examples", + "clients" + ] }, { "group": "Tutorials", @@ -61,6 +66,12 @@ "docs/concepts/sampling", "docs/concepts/transports" ] + }, + { + "group": "Development", + "pages": [ + "development/contributing" + ] } ], "footerSocials": { From 880471f47c6a09dc8519df06f9dec1072c936e6a Mon Sep 17 00:00:00 2001 From: Justin Spahr-Summers Date: Tue, 17 Dec 2024 15:37:24 +0000 Subject: [PATCH 2/5] Document what we're thinking about in terms of roadmap --- development/roadmap.mdx | 57 +++++++++++++++++++++++++++++++++++++++++ mint.json | 1 + 2 files changed, 58 insertions(+) create mode 100644 development/roadmap.mdx diff --git a/development/roadmap.mdx b/development/roadmap.mdx new file mode 100644 index 0000000..7e335ab --- /dev/null +++ b/development/roadmap.mdx @@ -0,0 +1,57 @@ +--- +title: Roadmap +description: Our plans for evolving Model Context Protocol +--- + +The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and future direction, though these may change significantly as the project develops. + +The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. + +We encourage community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts. + +## Remote MCP Support + +Our top priority is enabling [remote MCP connections](https://github.com/modelcontextprotocol/specification/discussions/102), allowing clients to securely connect to MCP servers over the internet. Key initiatives include: + +- [**Authentication & Authorization**](https://github.com/modelcontextprotocol/specification/discussions/64): Adding standardized auth capabilities, particularly focused on OAuth 2.0 support. + +- [**Service Discovery**](https://github.com/modelcontextprotocol/specification/discussions/69): Defining how clients can discover and connect to remote MCP servers, perhaps through a mechanism like a well known URI for MCP. + +- [**Stateless Operations**](https://github.com/modelcontextprotocol/specification/discussions/102): Ensuring MCP servers can operate in serverless environments, where they will need to be mostly stateless. + +## Reference Implementations + +To help developers build with MCP, we want to offer documentation for: + +- **Client Examples**: Comprehensive reference client implementation(s), demonstrating all protocol features +- **Protocol Drafting**: Streamlined process for proposing and incorporating new protocol features + +## Distribution & Discovery + +Looking ahead, we're exploring ways to make MCP servers more accessible. Some areas we may investigate include: + +- **Package Management**: Standardized packaging format for MCP servers +- **Installation Tools**: Simplified server installation across MCP clients +- **Sandboxing**: Improved security through server isolation +- **Server Registry**: A common directory for discovering available MCP servers + +## Agent Support + +We're expanding MCP's capabilities for [complex agentic workflows](https://github.com/modelcontextprotocol/specification/discussions/111), particularly focusing on: + +- [**Hierarchical Agent Systems**](https://github.com/modelcontextprotocol/specification/discussions/94): Improved support for trees of agents through namespacing and topology awareness. + +- [**Interactive Workflows**](https://github.com/modelcontextprotocol/specification/issues/97): Better handling of user permissions and information requests across agent hierarchies, and ways to send output to users instead of models. + +- [**Streaming Results**](https://github.com/modelcontextprotocol/specification/issues/117): Real-time updates from long-running agent operations. + +## Broader Ecosystem + +We're also invested in: + +- **Community-Led Standards Development**: Fostering a collaborative ecosystem where all AI providers can help shape MCP as an open standard through equal participation and shared governance, ensuring it meets the needs of diverse AI applications and use cases. +- [**Additional Modalities**](https://github.com/modelcontextprotocol/specification/discussions/88): Expanding beyond text to support audio, video, and other formats. + +## Get Involved + +We welcome community participation in shaping MCP's future. Visit our [GitHub Discussions](https://github.com/orgs/modelcontextprotocol/discussions) to join the conversation and contribute your ideas. diff --git a/mint.json b/mint.json index ffbf4fa..93fb64b 100644 --- a/mint.json +++ b/mint.json @@ -70,6 +70,7 @@ { "group": "Development", "pages": [ + "development/roadmap", "development/contributing" ] } From cdbe3591e352a21e8d60d43b8acf4462a4054560 Mon Sep 17 00:00:00 2001 From: Justin Spahr-Summers Date: Tue, 17 Dec 2024 16:12:56 +0000 Subject: [PATCH 3/5] Clarify this is H1 2025 --- development/roadmap.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/development/roadmap.mdx b/development/roadmap.mdx index 7e335ab..2e8e087 100644 --- a/development/roadmap.mdx +++ b/development/roadmap.mdx @@ -1,9 +1,9 @@ --- title: Roadmap -description: Our plans for evolving Model Context Protocol +description: Our plans for evolving Model Context Protocol (H1 2025) --- -The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and future direction, though these may change significantly as the project develops. +The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and future direction for **the first half of 2025**, though these may change significantly as the project develops. The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. From 9031824639e20e154e514b6da81a923defdc4593 Mon Sep 17 00:00:00 2001 From: Justin Spahr-Summers Date: Tue, 17 Dec 2024 20:10:47 +0000 Subject: [PATCH 4/5] Apply suggestions from code review Co-authored-by: David Soria Parra <167242713+dsp-ant@users.noreply.github.com> --- development/roadmap.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/development/roadmap.mdx b/development/roadmap.mdx index 2e8e087..0b1cbf4 100644 --- a/development/roadmap.mdx +++ b/development/roadmap.mdx @@ -15,7 +15,7 @@ Our top priority is enabling [remote MCP connections](https://github.com/modelco - [**Authentication & Authorization**](https://github.com/modelcontextprotocol/specification/discussions/64): Adding standardized auth capabilities, particularly focused on OAuth 2.0 support. -- [**Service Discovery**](https://github.com/modelcontextprotocol/specification/discussions/69): Defining how clients can discover and connect to remote MCP servers, perhaps through a mechanism like a well known URI for MCP. +- [**Service Discovery**](https://github.com/modelcontextprotocol/specification/discussions/69): Defining how clients can discover and connect to remote MCP servers. - [**Stateless Operations**](https://github.com/modelcontextprotocol/specification/discussions/102): Ensuring MCP servers can operate in serverless environments, where they will need to be mostly stateless. @@ -51,6 +51,7 @@ We're also invested in: - **Community-Led Standards Development**: Fostering a collaborative ecosystem where all AI providers can help shape MCP as an open standard through equal participation and shared governance, ensuring it meets the needs of diverse AI applications and use cases. - [**Additional Modalities**](https://github.com/modelcontextprotocol/specification/discussions/88): Expanding beyond text to support audio, video, and other formats. +- [**Standardization**] Considering standardization through a standardization body. ## Get Involved From 4270ebbff37f13343fe46acb67d7aff8a337c3df Mon Sep 17 00:00:00 2001 From: Justin Spahr-Summers Date: Tue, 17 Dec 2024 20:14:09 +0000 Subject: [PATCH 5/5] Address other review comments --- development/roadmap.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/development/roadmap.mdx b/development/roadmap.mdx index 0b1cbf4..4e4649c 100644 --- a/development/roadmap.mdx +++ b/development/roadmap.mdx @@ -5,7 +5,7 @@ description: Our plans for evolving Model Context Protocol (H1 2025) The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and future direction for **the first half of 2025**, though these may change significantly as the project develops. -The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. +The ideas presented here are not commitments—we may solve these challenges differently than described, or some may not materialize at all. This is also not an _exhaustive_ list; we may incorporate work that isn't mentioned here. We encourage community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts. @@ -17,7 +17,7 @@ Our top priority is enabling [remote MCP connections](https://github.com/modelco - [**Service Discovery**](https://github.com/modelcontextprotocol/specification/discussions/69): Defining how clients can discover and connect to remote MCP servers. -- [**Stateless Operations**](https://github.com/modelcontextprotocol/specification/discussions/102): Ensuring MCP servers can operate in serverless environments, where they will need to be mostly stateless. +- [**Stateless Operations**](https://github.com/modelcontextprotocol/specification/discussions/102): Thinking about whether MCP could encompass serverless environments too, where they will need to be mostly stateless. ## Reference Implementations