← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGoogle Maps MCP Server18 Google Maps tools for AI agents — geocode, route, search, and reason about locations.Hostinger API MCP ServerOfficial MCP server for Hostinger API.
FMRS56 / 100 · C70 / 100 · B
Reliability6 / 2011 / 20
Security and permissions12 / 2014 / 20
Maintenance12 / 2016 / 20
Documentation13 / 2015 / 20
Setup experience13 / 2014 / 20
Best for
  • AI agents requiring geospatial capabilities
  • Travel planning applications
  • Local search and logistics optimization
  • Local SEO analysis
  • Developers needing map visualization, route optimization
  • Developers using Hostinger services.
  • Users who want to automate hosting tasks through AI assistants.
Not for
  • Simple chatbots that don't need Google Maps features
  • Deployments needing high-precision location but unwilling to rely on external API keys
  • Use cases requiring real-time traffic flow, street view, or turn-by-turn mobile navigation (not provided)
  • Scenarios needing official Google support, as this is a community project
  • Users not on Hostinger.
  • Those needing to manage other cloud providers.
Required permissions
  • Requires a valid Google Maps API key (`GOOGLE_MAPS_API_KEY`), with Places API (New) and Routes API enabled.
  • Server makes external network requests to Google Maps APIs.
  • All tools are annotated with `readOnlyHint: true` and `destructiveHint: false` — MCP clients can auto-approve without user confirmation.
  • Tool enabling can be filtered via `GOOGLE_MAPS_ENABLED_TOOLS` environment variable.
  • Requires a Hostinger API token or OAuth authorization.
  • Can read and modify domains, hosting resources, etc., depending on token scopes.
Risks and side effects
  • API key leakage risk: handle carefully, do not commit to public repositories.
  • Cost risk: high usage may incur charges on Google Cloud account; set quotas and budgets.
  • Data privacy: addresses and coordinates sent to APIs may be sensitive.
  • Tools are read-only but could be used for malicious tracking.
  • High-risk operations (e.g., deleting websites) are irreversible.
  • API token leakage could allow misuse of resources.
  • Mistakes could cause website or service outages.
Supported clientsClaude Desktop, Cursor, VS CodeClaude Desktop, Cursor, Gemini CLI
Tools18100