Skip to main content
Glama
A1-x-Tech

mcp-google-business

by A1-x-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-google-business

No user-submitted related servers found.

    Related Servers

    • ReputeMap MCP by reputemap

      ReputeMap MCPofficial

      reputemap
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage Google Business Profile reviews, including a filterable review inbox, per-location stats, and honest review-request campaigns.
      29 npm
      MIT

    • Local Business Data MCP Server

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Enables access to Google Maps business data including search, reviews, photos, and geocoding. Supports searching businesses by location, area, or coordinates, retrieving detailed business information, reviews, and performing reverse geocoding operations.
      13
      MIT

    • Google Maps MCP Server

      adityak74
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search places, retrieve place details, reviews, photos, business posts, and contributor review histories from Google Maps through natural language, with no API keys or paid billing required.
      6
      MIT

    • Google Analytics 4 MCP Server

      stucchi
      A
      license
      B
      quality
      D
      maintenance
      Enables managing Google Analytics 4 properties, data streams, conversions, and running reports using natural language through the Admin and Data APIs.
      23
      19 PyPI
      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.2/5.0

    Scored across 26 tools

    Disambiguation4/5

    Each tool targets a distinct resource or workflow step, so an agent can generally tell them apart. The only close pairs are get_daily_metrics vs fetch_multi_daily_metrics and update_location vs update_location_attributes, but their descriptions clearly separate single vs batched and location fields vs attributes.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun snake_case pattern like list_locations, create_local_post, and delete_local_post. Minor deviations like auth_status, setup_instructions, raw_request, and the get_/fetch_ metric pair prevent a perfect score.

    Tool Count4/5

    26 tools is high, but the server covers a genuinely broad domain: OAuth setup, accounts, locations, attributes, reviews, local posts, performance metrics, and an escape hatch. The auth/onboarding block inflates the count, though each step is distinct and earns its place.

    Completeness4/5

    Core workflows are covered end-to-end: authentication, account/location listing, location updates, attribute management, review replies, local post CRUD, and performance metrics. Obvious gaps like create/delete location and media endpoints are workable through raw_request but would be cleaner as dedicated tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources