-
Notifications
You must be signed in to change notification settings - Fork 323
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
added mcp_tool + Example #335
base: main
Are you sure you want to change the base?
Conversation
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.
Looks pretty straightforward. I have other plans on making working with tools in Rig much easier but I think my main suggestion here is using optional features for rig itself.
I think separately, mcp-core
currently aligns itself to actix and other async web stuff but theoretically, it might be worthwhile to make it framework agnostic (similar to how rig
doesn't force tokio
). this could be a future goal!
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.
looks pretty good!
Minimal implementation of MCP tooling via mcp-core. Includes an example of starting an MCP Server, creating an MCP client, and adding those MCP tools to a rig agent and executing a tool call.
Currently using
mcp-core
dep while the officialmcp/rust-sdk
is in development as it is not currently on crates.io.mcp-core
is contributing its efforts to the official repo in the meantime.