Skip to content

Commit 75bfa63

Browse files
drewbentdrewbent
committed
Merge branch 'main' into drewbent/personas
2 parents 82def68 + 7d5ca3d commit 75bfa63

File tree

9 files changed

+214
-4
lines changed

9 files changed

+214
-4
lines changed

‎clients.mdx

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ This page provides an overview of applications that support the Model Context Pr
1616
| [Continue][Continue] | ✅ | ✅ | ✅ | ❌ | ❌ | Full support for all MCP features |
1717
| [GenAIScript][GenAIScript] | ❌ | ❌ | ✅ | ❌ | ❌ | Supports tools. |
1818
| [Cline][Cline] | ✅ | ❌ | ✅ | ❌ | ❌ | Supports tools and resources. |
19+
| [LibreChat][LibreChat] | ❌ | ❌ | ✅ | ❌ | ❌ | Supports tools for Agents |
20+
| [TheiaAI/TheiaIDE][TheiaAI/TheiaIDE] | ❌ | ❌ | ✅ | ❌ | ❌ | Supports tools for Agents in Theia AI and the AI-powered Theia IDE |
1921

2022
[Claude]: https://claude.ai/download
2123
[Zed]: https://zed.dev
@@ -24,6 +26,8 @@ This page provides an overview of applications that support the Model Context Pr
2426
[Continue]: https://github.com/continuedev/continue
2527
[GenAIScript]: https://microsoft.github.io/genaiscript/reference/scripts/mcp-tools/
2628
[Cline]: https://github.com/cline/cline
29+
[LibreChat]: https://github.com/danny-avila/LibreChat
30+
[TheiaAI/TheiaIDE]: https://eclipsesource.com/blogs/2024/12/19/theia-ide-and-theia-ai-support-mcp/
2731

2832
[Resources]: https://modelcontextprotocol.io/docs/concepts/resources
2933
[Prompts]: https://modelcontextprotocol.io/docs/concepts/prompts
@@ -95,6 +99,29 @@ Programmatically assemble prompts for LLMs using [GenAIScript](https://microsoft
9599
- Share custom MCP servers Cline creates with others via the `~/Documents/Cline/MCP` directory
96100
- Displays configured MCP servers along with their tools, resources, and any error logs
97101

102+
### LibreChat
103+
[LibreChat](https://github.com/danny-avila/LibreChat) is an open-source, customizable AI chat UI that supports multiple AI providers, now including MCP integration.
104+
105+
**Key features:**
106+
- Extend current tool ecosystem, including [Code Interpreter](https://www.librechat.ai/docs/features/code_interpreter) and Image generation tools, through MCP servers
107+
- Add tools to customizable [Agents](https://www.librechat.ai/docs/features/agents), using a variety of LLMs from top providers
108+
- Open-source and self-hostable, with secure multi-user support
109+
- Future roadmap includes expanded MCP feature support
110+
111+
### TheiaAI/TheiaIDE
112+
[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.
113+
114+
**Key features:**
115+
- **Tool Integration**: Theia AI enables AI agents, including those in the Theia IDE, to utilize MCP servers for seamless tool interaction.
116+
- **Customizable Prompts**: The Theia IDE allows users to define and adapt prompts, dynamically integrating MCP servers for tailored workflows.
117+
- **Custom agents**: The Theia IDE supports creating custom agents that leverage MCP capabilities, enabling users to design dedicated workflows on the fly.
118+
119+
Theia AI and Theia IDE's MCP integration provide users with flexibility, making them powerful platforms for exploring and adapting MCP.
120+
121+
**Learn more:**
122+
- [Theia IDE and Theia AI MCP Announcement](https://eclipsesource.com/blogs/2024/12/19/theia-ide-and-theia-ai-support-mcp/)
123+
- [Download the AI-powered Theia IDE](https://theia-ide.org/)
124+
98125
## Adding MCP support to your application
99126

100127
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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
title: Contributing
3+
description: How to participate in Model Context Protocol development
4+
---
5+
6+
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.
7+
8+
All contributors must adhere to our [Code of Conduct](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md).
9+
10+
For questions and discussions, please use [GitHub Discussions](https://github.com/orgs/modelcontextprotocol/discussions).

‎development/roadmap.mdx

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
title: Roadmap
3+
description: Our plans for evolving Model Context Protocol (H1 2025)
4+
---
5+
6+
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.
7+
8+
<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>
9+
10+
We encourage community participation! Each section links to relevant discussions where you can learn more and contribute your thoughts.
11+
12+
## Remote MCP Support
13+
14+
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:
15+
16+
- [**Authentication & Authorization**](https://github.com/modelcontextprotocol/specification/discussions/64): Adding standardized auth capabilities, particularly focused on OAuth 2.0 support.
17+
18+
- [**Service Discovery**](https://github.com/modelcontextprotocol/specification/discussions/69): Defining how clients can discover and connect to remote MCP servers.
19+
20+
- [**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.
21+
22+
## Reference Implementations
23+
24+
To help developers build with MCP, we want to offer documentation for:
25+
26+
- **Client Examples**: Comprehensive reference client implementation(s), demonstrating all protocol features
27+
- **Protocol Drafting**: Streamlined process for proposing and incorporating new protocol features
28+
29+
## Distribution & Discovery
30+
31+
Looking ahead, we're exploring ways to make MCP servers more accessible. Some areas we may investigate include:
32+
33+
- **Package Management**: Standardized packaging format for MCP servers
34+
- **Installation Tools**: Simplified server installation across MCP clients
35+
- **Sandboxing**: Improved security through server isolation
36+
- **Server Registry**: A common directory for discovering available MCP servers
37+
38+
## Agent Support
39+
40+
We're expanding MCP's capabilities for [complex agentic workflows](https://github.com/modelcontextprotocol/specification/discussions/111), particularly focusing on:
41+
42+
- [**Hierarchical Agent Systems**](https://github.com/modelcontextprotocol/specification/discussions/94): Improved support for trees of agents through namespacing and topology awareness.
43+
44+
- [**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.
45+
46+
- [**Streaming Results**](https://github.com/modelcontextprotocol/specification/issues/117): Real-time updates from long-running agent operations.
47+
48+
## Broader Ecosystem
49+
50+
We're also invested in:
51+
52+
- **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.
53+
- [**Additional Modalities**](https://github.com/modelcontextprotocol/specification/discussions/88): Expanding beyond text to support audio, video, and other formats.
54+
- [**Standardization**] Considering standardization through a standardization body.
55+
56+
## Get Involved
57+
58+
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

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: "Roots"
3+
description: "Understanding roots in MCP"
4+
---
5+
6+
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.
7+
8+
## What are Roots?
9+
10+
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.
11+
12+
For example, roots could be:
13+
14+
```
15+
file:///home/user/projects/myapp
16+
https://api.example.com/v1
17+
```
18+
19+
## Why Use Roots?
20+
21+
Roots serve several important purposes:
22+
23+
1. **Guidance**: They inform servers about relevant resources and locations
24+
2. **Clarity**: Roots make it clear which resources are part of your workspace
25+
3. **Organization**: Multiple roots let you work with different resources simultaneously
26+
27+
## How Roots Work
28+
29+
When a client supports roots, it:
30+
31+
1. Declares the `roots` capability during connection
32+
2. Provides a list of suggested roots to the server
33+
3. Notifies the server when roots change (if supported)
34+
35+
While roots are informational and not strictly enforcing, servers should:
36+
37+
1. Respect the provided roots
38+
2. Use root URIs to locate and access resources
39+
3. Prioritize operations within root boundaries
40+
41+
## Common Use Cases
42+
43+
Roots are commonly used to define:
44+
45+
- Project directories
46+
- Repository locations
47+
- API endpoints
48+
- Configuration locations
49+
- Resource boundaries
50+
51+
## Best Practices
52+
53+
When working with roots:
54+
55+
1. Only suggest necessary resources
56+
2. Use clear, descriptive names for roots
57+
3. Monitor root accessibility
58+
4. Handle root changes gracefully
59+
60+
## Example
61+
62+
Here's how a typical MCP client might expose roots:
63+
64+
```json
65+
{
66+
"roots": [
67+
{
68+
"uri": "file:///home/user/projects/frontend",
69+
"name": "Frontend Repository"
70+
},
71+
{
72+
"uri": "https://api.example.com/v1",
73+
"name": "API Endpoint"
74+
}
75+
]
76+
}
77+
```
78+
79+
This configuration suggests the server focus on both a local repository and an API endpoint while keeping them logically separated.

‎docs/concepts/tools.mdx

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,12 @@ Here's an example of implementing a basic tool in an MCP server:
7373
if (request.params.name === "calculate_sum") {
7474
const { a, b } = request.params.arguments;
7575
return {
76-
toolResult: a + b
76+
content: [
77+
{
78+
type: "text",
79+
text: String(a + b)
80+
}
81+
]
7782
};
7883
}
7984
throw new Error("Tool not found");

‎docs/tools/debugging.mdx

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,23 @@ Use the Network panel to inspect:
8080

8181
## Common issues
8282

83+
### Working directory
84+
85+
When using MCP servers with Claude Desktop:
86+
87+
- 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
88+
- Always use absolute paths in your configuration and `.env` files to ensure reliable operation
89+
- For testing servers directly via command line, the working directory will be where you run the command
90+
91+
For example in `claude_desktop_config.json`, use:
92+
```json
93+
{
94+
"command": "npx",
95+
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/username/data"]
96+
}
97+
```
98+
Instead of relative paths like `./data`
99+
83100
### Environment variables
84101

85102
MCP servers inherit only a subset of environment variables automatically, like `USER`, `HOME`, and `PATH`.
@@ -105,6 +122,7 @@ Common initialization problems:
105122
- Incorrect server executable path
106123
- Missing required files
107124
- Permission problems
125+
- Try using an absolute path for `command`
108126

109127
2. **Configuration Errors**
110128
- Invalid JSON syntax

‎introduction.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,4 +170,4 @@ Dive deeper into MCP's core concepts and capabilities:
170170

171171
## Contributing
172172

173-
Want to contribute? Check out [@modelcontextprotocol](https://github.com/modelcontextprotocol) on GitHub to join our growing community of developers building with MCP.
173+
Want to contribute? Check out our [Contributing Guide](/development/contributing) to learn how you can help improve MCP.

‎mint.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,11 @@
3131
"icon": "square-js",
3232
"url": "https://github.com/modelcontextprotocol/typescript-sdk"
3333
},
34+
{
35+
"name": "Kotlin SDK",
36+
"icon": "square-k",
37+
"url": "https://github.com/modelcontextprotocol/kotlin-sdk"
38+
},
3439
{
3540
"name": "Specification",
3641
"icon": "book",
@@ -72,8 +77,16 @@
7277
"docs/concepts/prompts",
7378
"docs/concepts/tools",
7479
"docs/concepts/sampling",
80+
"docs/concepts/roots",
7581
"docs/concepts/transports"
7682
]
83+
},
84+
{
85+
"group": "Development",
86+
"pages": [
87+
"development/roadmap",
88+
"development/contributing"
89+
]
7790
}
7891
],
7992
"footerSocials": {

‎quickstart/server.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -453,7 +453,7 @@ In this case, we'll add our single weather server like so:
453453
"command": "uv",
454454
"args": [
455455
"--directory",
456-
"C:\\ABSOLUTE\PATH\TO\PARENT\FOLDER\weather",
456+
"C:\\ABSOLUTE\\PATH\\TO\\PARENT\\FOLDER\\weather",
457457
"run",
458458
"weather"
459459
]
@@ -974,7 +974,7 @@ In this case, we'll add our single weather server like so:
974974
"weather": {
975975
"command": "node",
976976
"args": [
977-
"C:\\PATH\TO\PARENT\FOLDER\weather\build\index.js"
977+
"C:\\PATH\\TO\\PARENT\\FOLDER\\weather\\build\\index.js"
978978
]
979979
}
980980
}

0 commit comments

Comments
 (0)