You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MCP standard is protocol-agnostic and can be built upon any transport protocol. Currently, only local MCP tools are supported by providing an StdioServerParameters.In particular, SSE support comes ootb.
I think it would be great if we could have a higher level implementation of MCP tools to allow for more flexibility.
Currently the way I see it is we could make .from_mcp() accept an MCP client from the official Python SDK (or maybe just make it an abstract class if people want to use their custom implementation). Then the ToolCollection would handle tool discovery and calling through the client and provide the tools to the agent the standard way.
The only problem would maybe be the async nature of MCP tool calls, but that could be handled the same way MCPAdapt does it, or through proper support of async calls (#145).
The text was updated successfully, but these errors were encountered:
The MCP standard is protocol-agnostic and can be built upon any transport protocol. Currently, only local MCP tools are supported by providing an
StdioServerParameters
.In particular, SSE support comes ootb.I think it would be great if we could have a higher level implementation of MCP tools to allow for more flexibility.
Currently the way I see it is we could make
.from_mcp()
accept an MCP client from the official Python SDK (or maybe just make it an abstract class if people want to use their custom implementation). Then theToolCollection
would handle tool discovery and calling through the client and provide the tools to the agent the standard way.The only problem would maybe be the async nature of MCP tool calls, but that could be handled the same way MCPAdapt does it, or through proper support of async calls (#145).
The text was updated successfully, but these errors were encountered: