In-depth architectural comparison of the Google Health MCP and Google Slides MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Google Health MCP
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Google Slides MCP
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Google Health MCP if you need specialized Developer Tools tools running via a local process. Choose Google Slides MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Google Health MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Google Health MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Google Slides MCP belongs to Developer Tools using local stdio subprocess. Select Google Health MCP when you need capabilities focused on developer tools and Google Slides MCP when you require tools for developer tools.