Merge branch 'main' into drewbent/personas

Author: drewbent

clients.mdx

@@ -16,6 +16,8 @@ This page provides an overview of applications that support the Model Context Pr
 | [Continue][Continue]      | ✅         | ✅         | ✅       | ❌          | ❌     | Full support for all MCP features                 |
 | [GenAIScript][GenAIScript]  | ❌         | ❌         | ✅       | ❌          | ❌     | Supports tools. |
 | [Cline][Cline]      | ✅         | ❌         | ✅       | ❌          | ❌     | Supports tools and resources.                 |
+| [LibreChat][LibreChat]     | ❌         | ❌         | ✅       | ❌          | ❌     | Supports tools for Agents    |
+| [TheiaAI/TheiaIDE][TheiaAI/TheiaIDE]     | ❌         | ❌         | ✅       | ❌          | ❌     | Supports tools for Agents in Theia AI and the AI-powered Theia IDE    |
 
 [Claude]: https://claude.ai/download
 [Zed]: https://zed.dev
@@ -24,6 +26,8 @@ This page provides an overview of applications that support the Model Context Pr
 [Continue]: https://github.com/continuedev/continue
 [GenAIScript]: https://microsoft.github.io/genaiscript/reference/scripts/mcp-tools/
 [Cline]: https://github.com/cline/cline
+[LibreChat]: https://github.com/danny-avila/LibreChat
+[TheiaAI/TheiaIDE]: https://eclipsesource.com/blogs/2024/12/19/theia-ide-and-theia-ai-support-mcp/
 
 [Resources]: https://modelcontextprotocol.io/docs/concepts/resources
 [Prompts]: https://modelcontextprotocol.io/docs/concepts/prompts
@@ -95,6 +99,29 @@ Programmatically assemble prompts for LLMs using [GenAIScript](https://microsoft
 - Share custom MCP servers Cline creates with others via the `~/Documents/Cline/MCP` directory
 - Displays configured MCP servers along with their tools, resources, and any error logs
 
+### LibreChat
+[LibreChat](https://github.com/danny-avila/LibreChat) is an open-source, customizable AI chat UI that supports multiple AI providers, now including MCP integration.
+
+**Key features:**
+- Extend current tool ecosystem, including [Code Interpreter](https://www.librechat.ai/docs/features/code_interpreter) and Image generation tools, through MCP servers
+- Add tools to customizable [Agents](https://www.librechat.ai/docs/features/agents), using a variety of LLMs from top providers
+- Open-source and self-hostable, with secure multi-user support
+- Future roadmap includes expanded MCP feature support
+
+### TheiaAI/TheiaIDE
+[Theia AI](https://eclipsesource.com/blogs/2024/10/07/introducing-theia-ai/) is a framework for building AI-enhanced tools and IDEs. The [AI-powered Theia IDE](https://eclipsesource.com/blogs/2024/10/08/introducting-ai-theia-ide/) is an open and flexible development environment built on Theia AI.
+
+**Key features:**
+- **Tool Integration**: Theia AI enables AI agents, including those in the Theia IDE, to utilize MCP servers for seamless tool interaction.
+- **Customizable Prompts**: The Theia IDE allows users to define and adapt prompts, dynamically integrating MCP servers for tailored workflows.
+- **Custom agents**: The Theia IDE supports creating custom agents that leverage MCP capabilities, enabling users to design dedicated workflows on the fly.
+
+Theia AI and Theia IDE's MCP integration provide users with flexibility, making them powerful platforms for exploring and adapting MCP.
+
+**Learn more:**
+- [Theia IDE and Theia AI MCP Announcement](https://eclipsesource.com/blogs/2024/12/19/theia-ide-and-theia-ai-support-mcp/)
+- [Download the AI-powered Theia IDE](https://theia-ide.org/)
+
 ## Adding MCP support to your application
 
 If you've added MCP support to your application, we encourage you to submit a pull request to add it to this list. MCP integration can provide your users with powerful contextual AI capabilities and make your application part of the growing MCP ecosystem.

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).

development/roadmap.mdx

@@ -0,0 +1,58 @@
+---
+title: Roadmap
+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.
+
+<Note>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.</Note>
+
+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.
+
+- [**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
+
+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.
+- [**Standardization**] Considering standardization through a standardization body.
+
+## 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.

docs/concepts/roots.mdx

@@ -0,0 +1,79 @@
+---
+title: "Roots"
+description: "Understanding roots in MCP"
+---
+
+Roots are a concept in MCP that define the boundaries where servers can operate. They provide a way for clients to inform servers about relevant resources and their locations.
+
+## What are Roots?
+
+A root is a URI that a client suggests a server should focus on. When a client connects to a server, it declares which roots the server should work with. While primarily used for filesystem paths, roots can be any valid URI including HTTP URLs.
+
+For example, roots could be:
+
+```
+file:///home/user/projects/myapp
+https://api.example.com/v1
+```
+
+## Why Use Roots?
+
+Roots serve several important purposes:
+
+1. **Guidance**: They inform servers about relevant resources and locations
+2. **Clarity**: Roots make it clear which resources are part of your workspace
+3. **Organization**: Multiple roots let you work with different resources simultaneously
+
+## How Roots Work
+
+When a client supports roots, it:
+
+1. Declares the `roots` capability during connection
+2. Provides a list of suggested roots to the server
+3. Notifies the server when roots change (if supported)
+
+While roots are informational and not strictly enforcing, servers should:
+
+1. Respect the provided roots
+2. Use root URIs to locate and access resources
+3. Prioritize operations within root boundaries
+
+## Common Use Cases
+
+Roots are commonly used to define:
+
+- Project directories
+- Repository locations
+- API endpoints
+- Configuration locations
+- Resource boundaries
+
+## Best Practices
+
+When working with roots:
+
+1. Only suggest necessary resources
+2. Use clear, descriptive names for roots
+3. Monitor root accessibility
+4. Handle root changes gracefully
+
+## Example
+
+Here's how a typical MCP client might expose roots:
+
+```json
+{
+  "roots": [
+    {
+      "uri": "file:///home/user/projects/frontend",
+      "name": "Frontend Repository"
+    },
+    {
+      "uri": "https://api.example.com/v1",
+      "name": "API Endpoint"
+    }
+  ]
+}
+```
+
+This configuration suggests the server focus on both a local repository and an API endpoint while keeping them logically separated.

docs/concepts/tools.mdx

@@ -73,7 +73,12 @@ Here's an example of implementing a basic tool in an MCP server:
       if (request.params.name === "calculate_sum") {
         const { a, b } = request.params.arguments;
         return {
-          toolResult: a + b
+          content: [
+            {
+              type: "text",
+              text: String(a + b)
+            }
+          ]
         };
       }
       throw new Error("Tool not found");

docs/tools/debugging.mdx

@@ -80,6 +80,23 @@ Use the Network panel to inspect:
 
 ## Common issues
 
+### Working directory
+
+When using MCP servers with Claude Desktop:
+
+- The working directory for servers launched via `claude_desktop_config.json` may be undefined (like `/` on macOS) since Claude Desktop could be started from anywhere
+- Always use absolute paths in your configuration and `.env` files to ensure reliable operation
+- For testing servers directly via command line, the working directory will be where you run the command
+
+For example in `claude_desktop_config.json`, use:
+```json
+{
+  "command": "npx",
+  "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/username/data"]
+}
+```
+Instead of relative paths like `./data`
+
 ### Environment variables
 
 MCP servers inherit only a subset of environment variables automatically, like `USER`, `HOME`, and `PATH`.
@@ -105,6 +122,7 @@ Common initialization problems:
    - Incorrect server executable path
    - Missing required files
    - Permission problems
+   - Try using an absolute path for `command`
 
 2. **Configuration Errors**
    - Invalid JSON syntax

introduction.mdx

@@ -170,4 +170,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.
+Want to contribute? Check out our [Contributing Guide](/development/contributing) to learn how you can help improve MCP.

mint.json

@@ -31,6 +31,11 @@
       "icon": "square-js",
       "url": "https://github.com/modelcontextprotocol/typescript-sdk"
     },
+    {
+      "name": "Kotlin SDK",
+      "icon": "square-k",
+      "url": "https://github.com/modelcontextprotocol/kotlin-sdk"
+    },
     {
       "name": "Specification",
       "icon": "book",
@@ -72,8 +77,16 @@
         "docs/concepts/prompts",
         "docs/concepts/tools",
         "docs/concepts/sampling",
+        "docs/concepts/roots",
         "docs/concepts/transports"
       ]
+    },
+    {
+      "group": "Development",
+      "pages": [
+        "development/roadmap",
+        "development/contributing"
+      ]
     }
   ],
   "footerSocials": {

quickstart/server.mdx

@@ -453,7 +453,7 @@ In this case, we'll add our single weather server like so:
             "command": "uv",
             "args": [
                 "--directory",
-                "C:\\ABSOLUTE\PATH\TO\PARENT\FOLDER\weather",
+                "C:\\ABSOLUTE\\PATH\\TO\\PARENT\\FOLDER\\weather",
                 "run",
                 "weather"
             ]
@@ -974,7 +974,7 @@ In this case, we'll add our single weather server like so:
         "weather": {
             "command": "node",
             "args": [
-                "C:\\PATH\TO\PARENT\FOLDER\weather\build\index.js"
+                "C:\\PATH\\TO\\PARENT\\FOLDER\\weather\\build\\index.js"
             ]
         }
     }