The MCP connector list tells you a tool shows up, not whether it does anything useful
Bodil Biering
Vincent has around 15 MCP connectors set up. Not all of them turned out to be plug and play.
Zapier is the clearest example. The whole point of connecting Zapier is to manage your Zaps — the automations themselves. That’s the one thing you can’t do through the MCP connection. It’s listed as an MCP connector. It just doesn’t do the thing you’d want it for.
His read on it: a lot of tools on these connector lists have “some MCP,” but it doesn’t have the full range. The listing tells you the tool shows up. It doesn’t tell you whether it does anything useful once it’s there.
Cyberjuice actually has the full range — everything that’s in Cyberjuice is reachable through MCP
So the lesson isn’t “check if a tool supports MCP.” It’s “check if MCP covers the specific thing you’re connecting it for.” Those are different questions, and the connector list only answers the first one.
