4 ms·
I hear that multiple MCP tools eat up your context. See last video Indy Dev Dan. Maybe one day this becomes now relevant, but today? Isn’t it better to stick t
by stpedgwdgfhgdd 1y ago
I hear that multiple MCP tools eat up your context. See last video Indy Dev Dan.
Maybe one day this becomes now relevant, but today? Isn’t it better to stick to CLI tools? Lesser chance of supply chain attack if you stick to the vendor’s cli.
(I use 2 MCP servers in daily life, hesitant to add more)
- NicuCalcea 1y agoI think of it in terms of the individual tools, rather than the server. I have a server with ~30 tools, but I only need one, so I turned the rest off. The official GitHub MCP server is a good example of this, it has tools for everything from creating gists to managing teams, and you might really only need it to search repos or read issues.
- vidarh 1y agoAnd often you just need web access - e.g. Claude knows the Github API very well, and is perfectly capable of using quite a bit of it via curl, and so a lot of the time it's worth testing if the LLM knows how to access something directly before you start adding tools and mcp servers