31 ms·

I have trouble understanding the level of criticism about MCPs. As I understand it, it's just a tool that allows an LLM to communicate with other tools. People

I have trouble understanding the level of criticism about MCPs. As I understand it, it's just a tool that allows an LLM to communicate with other tools. People often talk about web APIs, but we should also consider the integration of local tools. For me, the integration is mind-blowing. When I tried the Playwright MCP integration [0][1] a few months ago, I really felt that after giving computers the ability to speak or communicate, we had now given them arms. I still get goosebumps thinking about it. [0]https://youtu.be/3NWy_sxD3Vc https://youtu.be/3NWy_sxD3Vc [1]https://github.com/microsoft/playwright-mcp https://github.com/microsoft/playwright-mcp [EDIT]

fendy3002 1y ago
IIRC people say that MCP is initially made for CLI / local tool execution for agent-based ai like cursor. And prople are skipping on service discovery. Making ai know what steps / operation is good.
ignoramous 1y ago
> For me, the integration is mind-blowing. When I tried the Playwright MCP integration ... I still get goosebumps thinking about it. Same. To see apps reverse engineered by LLMs with Ghidra [0] blew me away. It CTFed-out hard-coded access tokens and keys from .so's in seconds. [0] https://github.com/LaurieWired/GhidraMCP https://github.com/LaurieWired/GhidraMCP
magospietato 1y ago
Same here. Built a very rough Cucumber spec+Playwright test script generator on top of Playwright MCP and a Claude project. Pasting in a product owner's AC and and watching it browse through our test env for a few minutes before spitting out a passing - and passable - spec+test was kind of mind blowing.