Does each MCP server need to be dedicated to one tech only (alias Tool), like one MCP server for google drive, one for PostgreSQL, one for docker, etc.? Can’t we have one MCP server handling multiple Tools?
Does each MCP server need to be dedicated to one tech only (alias Tool), like one MCP server for google drive, one for PostgreSQL, one for docker, etc.? Can’t we have one MCP server handling multiple Tools?
You can create your own MCP Server, which handle all of these actions, but i won't find it efficient (except from some extreme cases). At the end of the day, all "tools" aka MCP Servers are combined into one toolbox and passed to Host through MCP Client, and Host is not aware of servers, because of MCP Client protocol proxy.
Does each MCP server need to be dedicated to one tech only (alias Tool), like one MCP server for google drive, one for PostgreSQL, one for docker, etc.? Can’t we have one MCP server handling multiple Tools?
You can create your own MCP Server, which handle all of these actions, but i won't find it efficient (except from some extreme cases). At the end of the day, all "tools" aka MCP Servers are combined into one toolbox and passed to Host through MCP Client, and Host is not aware of servers, because of MCP Client protocol proxy.