Expand MCP Workbench to support more MCP Client features#6785
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6785 +/- ##
==========================================
+ Coverage 80.42% 80.81% +0.39%
==========================================
Files 233 233
Lines 17922 18074 +152
==========================================
+ Hits 14413 14607 +194
+ Misses 3509 3467 -42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Improving the test coverage |
|
Looks good and trending in the right direction. Some things to consider in the future that @ekzhu and I have discussed include
|
ekzhu
left a comment
There was a problem hiding this comment.
Looks great! I think we should go with it
Also add exception logging in the actor loop
Using a real MCP server where possible. Had to put this server (mcp_server_comprehensive) outside of the tools directory to avoid module name collisions with the http directory in the tools folder
|
Pushed a small cleanup to the parsing of SamplingMessages. Also increased test coverage. |
Currently unsupported
|
@victordibia ready to merge (and squash ideally since I've added so many little fixup commtis) when you are! |
Why are these changes needed?
MCP Servers can request sampling from the MCP Host/Client's LLM.
Also exposed additional MCP ClientSession methods for listing and reading/getting prompts, resources, and resourceTemplates. This makes the McpWorkbench more like a full MCP Client.
Related issue number
N/A
Checks
Thoughts @ekzhu @victordibia ?