-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Swap MCP client implementations to rmcp #3634
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
Conversation
eb8bdb2 to
db5cf5b
Compare
|
|
||
| // Create console logging layer for development - INFO and above only | ||
| let console_layer = fmt::layer() | ||
| .with_writer(std::io::stderr) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change goes a bit further than strictly necessary as it moves all console logging to stderr, while we only truly needed to do that for mcp servers. But IMO we should always prefer stderr to stdout for logging.
|
.bundle |
macOS ARM64 Desktop App (Apple Silicon)📱 Download macOS Desktop App (arm64, signed) Instructions: This link is provided by nightly.link and will work even if you're not logged into GitHub. |
|
Thanks to @aharvard 's upgrading to rmcp 0.3.1 this pr became decently smaller 🎉 |
|
.bundle |
1 similar comment
|
.bundle |
|
FTR, this introduced #4481 |
This still leaves behind a small abstraction over the clients, which we could keep around or eventually get rid of.