In-depth architectural comparison of the Google Maps Places and Google Contacts 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 Maps Places
Developer Tools · Remote HTTP/SSE
Quality: 36/100 (Fair) | Auth: No auth required
Google Contacts
Developer Tools · Remote HTTP/SSE
Quality: 36/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Google Maps Places if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Google Contacts if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Google Maps Places when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Google Maps Places is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Google Contacts belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Google Maps Places when you need capabilities focused on developer tools and Google Contacts when you require tools for developer tools.