-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Passing client context to tools #375
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
Comments
I ran into the same issue. Instead of struggling to figure it out, I ended up writing my own MCP from scratch — it was much faster and way more optimized. |
I also had this problem because my app needs to add user data to the tool |
Can one of the contributors / maintainers comment, please? Perhaps there is a way to do this, that I haven't discovered? Thank you. |
I've opened a PR to hopefully solve this issue #574 |
(This may be related to #373)
I would like to be able to pass some "out of band" context to a tool in an MCP server. This would be separate from the arguments that are extracted by the LLM and provided to the tool function.
How do I pass this "extra" data to the tool?
Thank you for any help.
The text was updated successfully, but these errors were encountered: