What is the key difference between MCP Google Map and Geonames?

MCP Google Map belongs to the Location Services category with local stdio execution, while Geonames belongs to the Location Services category with cloud HTTP/SSE execution.

How do I install MCP Google Map or Geonames in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Google Map and Geonames free or paid?

MCP Google Map operates under a BYOK (Pay Provider Direct) model (API Key required). Geonames operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Google Map lists 18 tools with 4 views and 462 GitHub stars. Geonames lists 4 tools with 0 views and 0 GitHub stars.

Can I use both MCP Google Map and Geonames together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Google Map vs Geonames

In-depth architectural comparison of the MCP Google Map and Geonames 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

MCP Google Map

Location Services · Local stdio

Quality: 69/100 (Great) | Auth: API Key required

Geonames

Location Services · Remote HTTP/SSE

Quality: 49/100 (Fair) | Auth: No auth required

Verdict Summary: Choose MCP Google Map if you need specialized Location Services tools running via a local process. Choose Geonames if your workspace requires Location Services integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Google Map when:

You need dedicated capabilities in the Location Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: GOOGLE_MAPS_API_KEY.
Primary tools included: maps_search_nearby, maps_search_places, maps_place_details.

Explore MCP Google Map Details

Choose Geonames when:

You need dedicated capabilities in the Location Services domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: search_geonames, get_nearby, get_timezone.

Explore Geonames Details

Feature & Specification Comparison

Specification	MCP Google Map cablate Location Services	Geonames Location Services
Summary	Google Maps MCP server with 8 tools (geocode, search, directions, elevation), stdio + StreamableHTTP transport, Agent Skill definitions, and standalone exec CLI mode.	GeoNames MCP — GeoNames geographical database API
Category & Scope	Location Services	Location Services

Tools & Capabilities Breakdown

MCP Google Map Tools (18)

maps_search_nearby

Find places near a location by type (restaurant, cafe, hotel, etc.). Supports filtering by radius, rating, and open status.

maps_search_places

Free-text place search (e.g., "sushi restaurants in Tokyo"). Supports location bias, rating, open-now filters.

maps_place_details

Get full details for a place by its place_id — reviews, phone, website, hours. Optional `maxPhotos` param returns photo URLs.

maps_geocode

Convert an address or landmark name into GPS coordinates.

maps_reverse_geocode

Convert GPS coordinates into a street address.

maps_distance_matrix

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Google Map Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cablate-mcp-google-map": {
      "command": "npx",
      "args": [
        "-y",
        "@cablate/mcp-google-map"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "YOUR_GOOGLE_MAPS_API_KEY_HERE"
      }
    }
  }
}

Geonames Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "geonames": {
      "url": "https://gateway.pipeworx.io/geonames/mcp"
    }
  }
}

Frequently Asked Questions

MCP Google Map is categorized under Location Services and uses a local stdio subprocess. In contrast, Geonames belongs to Location Services using remote streaming HTTP/SSE transport. Select MCP Google Map when you need capabilities focused on location services and Geonames when you require tools for location services.

More alternatives to MCP Google Map More alternatives to Geonames Location Services category hub