Skip to main content
Glama
jrajasekera

goplaces MCP

by jrajasekera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to goplaces MCP

No user-submitted related servers found.

    Related Servers

    • Google Maps Geocoding MCP

      kevinwuhoo
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM clients to convert addresses to coordinates (forward geocoding), coordinates to addresses (reverse geocoding), and lookup Google Place IDs using the Google Maps Geocoding API with support for multiple languages and advanced filtering.
      3
      7 npm
      MIT

    • Google Maps MCP Server

      AIWerk
      A
      license
      A
      quality
      C
      maintenance
      Provides access to Google Maps Platform APIs for places search, geocoding, turn-by-turn directions, route matrices, elevation, and time zones. Enables natural language queries for location-based information and routing.
      11
      12 npm
      MIT

    • MCP Google Maps - stdio

      vicente-alvarado
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to access Google Maps services including geocoding, place search, directions, distance calculations, and elevation data through stdio communication. Provides comprehensive location-based functionality with direct Google Maps API integration.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (directions, photo, details, route_matrix), but search/resolve/autocomplete all convert text into places, and nearby/reverse_geocode both find places near coordinates. Descriptions provide use-case cues, so an agent can usually pick correctly, but the boundaries are not perfectly sharp.

    Naming Consistency5/5

    All tools share the goplaces_ prefix and snake_case naming with clear action/resource terms. There is no mixing of conventions such as camelCase, hyphens, or vague names.

    Tool Count5/5

    10 tools are well-scoped for a Google Places/Routes MCP, covering distinct API surfaces without obvious filler. Each tool maps to a meaningful location or routing capability.

    Completeness5/5

    The set covers search, nearby, autocomplete, details, photos, resolution, directions, route search, route matrix, and reverse geocoding. For a read-only places/routes domain, this provides comprehensive workflow coverage with no major dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources