7 Comments

I thought it's gonna be a bigger read honestly.

Expand full comment

Honestly, just searching for MCP on google now gives more information than these blog posts.

Expand full comment

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?

Expand full comment

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.

Expand full comment

Nice work, Really Appreciate your work. Thanks for in depth analysis. Lets connect

Expand full comment

Thank's for the newsletter! You do the great job, as always. <3

I've only spotted, that in this edition, mcp graphic could be a bit misleading.

It's worth to mention that - following origin documentation https://modelcontextprotocol.io/introduction - we don't have to have multiple mcp clients, each for one mcp server. There is a "Host with MCP Client" as a one block, which can handle connections to multiple servers. Just as you wrote down below the graphic :).

Just a small nit-pick :).

Expand full comment

A good introduction, excited for a more deeper dive in the future! <3

Expand full comment