-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganise? #6
Comments
Can someone come out and say a word? I agree with you. And it seems that the Router / Server / ByteTransport / BoundedService in crates/mcp-server and those defined errors should be moved to core to give the user a cleaner and leaner code example, can we do anything for this repository? |
The mcp-client and mcp-server are intended to be the dependencies that downstream crates would use directly! mcp-core is for shared content between both, mostly the types used in messages. The intent is that you can grab either client or server depending on what you need |
Just wanted to gently third that I find this repo quite confusing. As a rust developer I find |
Yes we're overdue for examples and documentation! The layout across a few crates (similar to |
Shouldn't https://github.com/modelcontextprotocol/rust-sdk/blob/main/crates/mcp-server/src/main.rs at least be an example, since it's a particular usage of an mcp-server (a counter server), showing how the library should be used? |
I completely agree with clearly documenting the project's examples and roadmap in the README. |
Pausing this reorganization for a second so we can coordinate several other MCP builders who have reached out |
May I gently suggest moving
crates/mcp-client
andcrates/mcp-server
to theexamples
directory? As they seem to be like sample implementations one could use, but are not actually part of the library as far as I can tell.The text was updated successfully, but these errors were encountered: