mcp-google-business
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_BUSINESS_CLIENT_ID | No | OAuth2 client id (Google Cloud Console). | |
| GOOGLE_BUSINESS_TIMEOUT_MS | No | Per-request timeout, ms. | 60000 |
| GOOGLE_BUSINESS_MAX_RETRIES | No | Retries on 429 (and 5xx/network for idempotent calls). | 3 |
| GOOGLE_BUSINESS_V4_API_BASE | No | Legacy v4 host override (reviews, posts). | https://mybusiness.googleapis.com |
| GOOGLE_BUSINESS_ACCESS_TOKEN | No | Ready-made access token (~1 h) instead of the trio above. | |
| GOOGLE_BUSINESS_CLIENT_SECRET | No | OAuth2 client secret. | |
| GOOGLE_BUSINESS_INFO_API_BASE | No | Business Information host override. | https://mybusinessbusinessinformation.googleapis.com |
| GOOGLE_BUSINESS_REFRESH_TOKEN | No | OAuth2 refresh token, scope business.manage. | |
| GOOGLE_BUSINESS_ACCOUNTS_API_BASE | No | Account Management host override. | https://mybusinessaccountmanagement.googleapis.com |
| GOOGLE_BUSINESS_PERFORMANCE_API_BASE | No | Performance host override. | https://businessprofileperformance.googleapis.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Google Business Profile (formerly Google My Business) manages the Search and Maps listings the authenticated Google account owns or manages: profile fields, reviews, local posts and metrics. It is not Google Ads, and a listing the account does not manage is unreachable — only profiles under the accounts list_accounts returns exist here. Creating a location and managing profile photos have no dedicated tool: raw_request is the only route; verifying a location is not possible at all (the Verifications API lives on a separate host this server cannot reach). If every call fails with a 429/403 quota error you are not sending too many requests: Business Profile APIs ship with a default quota of 0 QPM until Google approves the project's Application for Basic API Access (approved projects get 300 QPM per API), and writes additionally share a hard, non-raisable cap of 10 edits per minute per profile. An empty account list means the credentials' Google account manages no profile rather than a bad token. Writes are public and there is no undo: reply_to_review overwrites an existing reply without warning, deletions are final, and update_location's validateOnly is the only dry run available.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Shows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected. |
| setup_instructionsA | Step-by-step checklist for connecting this server to Google: creating a Google Cloud project and a Desktop-app OAuth client, publishing the consent screen (mandatory — Testing-mode refresh tokens die after 7 days), downloading the client JSON and handing its PATH to set_client. Works without any credentials; the checklist shortens to 'enable the API + log in' when an OAuth client is already configured (one client serves the whole mcp-google-* line). Never asks the user to paste secrets into the chat. |
| set_clientA | Saves the OAuth client credentials from the JSON file downloaded from Google Cloud Console ('Download JSON' on a Desktop-app client). Pass the file PATH — the secret must never be pasted into the chat. The client is stored once in the shared ~/.config/mcp-google-auth/client.json (owner-only) and reused by every mcp-google-* server; tokens stay per-server. After this, call start_login. |
| start_loginA | First step of connecting from the chat, without editing config files or restarting the client. Returns authorizeUrl — show it to the user as a clickable link and ask them to open it in the browser ON THIS MACHINE, pick the Google account and approve access. A one-shot listener on 127.0.0.1 catches Google's redirect; the code is exchanged locally and never passes through the chat. Does not open the browser itself. The attempt lives 10 minutes; when the browser shows the success page, call finish_login. |
| finish_loginA | Second step: waits up to 20 s for the browser consent to finish, saves the tokens to an owner-only file and verifies the login with a read-only identity call, returning the account email and the granted scopes. After success every tool works immediately — no client restart. If the user granted only part of the requested permissions, the login is still saved and missingScopes lists what will not work. Logging in under a different Google account replaces the previous login (its refresh token is revoked best-effort) and the response carries previousAccountEmail so the change never goes unnoticed. |
| logoutA | Revokes the stored token at Google (oauth2.googleapis.com/revoke) and deletes the local credentials file. Tokens supplied via env variables are NOT touched — remove them from the MCP client config manually; envTokenStillSet in the response says whether any are still in effect. |
| list_accountsA | Lists all Google Business Profile accounts the authenticated user can access (the personal account first). Each account has name (accounts/{id} — the id feeds the accountId of other tools), accountName, type (PERSONAL / LOCATION_GROUP / USER_GROUP / ORGANIZATION), role, and verificationState. The API caps pageSize at 20 (unusually small), so follow nextPageToken to see every account. |
| list_locationsA | Lists the business locations under an account (Business Information API). Each location's name is locations/{id} — that id feeds locationId everywhere else (including the Performance API and, together with the account id, the v4 reviews/posts tools). totalSize is only present when filter is set. Fields are limited by readMask; ask for metadata to get mapsUri/placeId/newReviewUri. |
| get_locationA | Returns one location by id (Business Information API; v1 uses the bare locations/{id} name, no account prefix). The readMask picks which fields come back: title, categories, storefrontAddress, phoneNumbers, websiteUri, regularHours, specialHours, openInfo, profile (description), storeCode, latlng, metadata (mapsUri, newReviewUri, placeId). |
| update_locationA | Updates fields of a location (PATCH with a required updateMask — only masked fields change). Pass the new values in |
| list_categoriesA | Lists/searches the reference taxonomy of business categories (e.g. gcid:restaurant). Category names (categories/gcid:...) feed location.categories on update_location and categoryName on list_attribute_metadata. view=FULL also returns serviceTypes and moreHoursTypes per category; filter narrows by display name, e.g. "displayName=coffee". |
| list_attribute_metadataA | Lists which attributes (e.g. wheelchair accessibility, wi-fi, payment options) are legal for a location or for a category+region. Pass locationId for a concrete location, OR categoryName+regionCode to explore. Each entry has parent (the attribute id for update_location_attributes), valueType (BOOL / ENUM / REPEATED_ENUM / URL), displayName, repeatable and valueMetadata (legal values). |
| update_location_attributesA | Updates attributes of a location (PATCH). Each attribute needs its name (attributes/{attribute_id} from list_attribute_metadata's parent field) plus values (BOOL/ENUM), uriValues (URL) or repeatedEnumValue ({setValues, unsetValues}). attributeMask defaults to the names of the attributes you pass; name an attribute in the mask with no values to clear it. Counts against the 10 edits/min per-profile cap. |
| search_chainsA | Searches business chains by name (exact/partial/fuzzy), ranked by relevance. Each chain has name (chains/{chain_id}), chainNames, websites and locationCount. Use the chain name when relating a location to its brand (location.relationshipData). |
| get_daily_metricsA | Returns a daily time series for ONE performance metric of a location: impressions by surface (Maps/Search × desktop/mobile), direction requests, call clicks, website clicks, conversations, bookings, food orders or menu clicks. Response: timeSeries.datedValues[] of {date{year,month,day}, value} — value is int64 serialized as a string; a missing value means no data for that day. Metrics for the most recent days are not available immediately (multi-day lag, typically a few days) — empty values near today are normal, not an error. |
| fetch_multi_daily_metricsA | Returns daily time series for SEVERAL performance metrics of a location in one call — same data as get_daily_metrics, but batched. Response: multiDailyMetricTimeSeries[].dailyMetricTimeSeries[] of {dailyMetric, timeSeries.datedValues[]}; values are int64 strings. Prefer this over several get_daily_metrics calls to save quota. Metrics for the most recent days are not available immediately (multi-day lag, typically a few days) — empty values near today are normal, not an error. |
| list_search_keyword_impressionsA | Returns the search keywords that surfaced the business on Google, month by month. Response: searchKeywordsCounts[] of {searchKeyword, insightsValue} — insightsValue is a UNION: either an exact {value} or a {threshold} for low-volume keywords (the true count is below it; never sum thresholds as exact counts). Months are calendar months; data for the current month appears with a lag. |
| list_reviewsA | Lists reviews of a location, newest-updated first by default. Response: reviews[] of {name, reviewId, reviewer{displayName, isAnonymous}, starRating (ONE..FIVE enum, not a number), comment, createTime, updateTime, reviewReply{comment, updateTime} if answered}, plus averageRating (1–5) and totalReviewCount. pageSize caps at 50. Reviews live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| get_reviewA | Returns one review by id — same shape as a list_reviews entry (starRating is an enum ONE..FIVE, reviewReply present only if the business already answered). Reviews live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| reply_to_reviewA | Creates OR replaces the business's public reply to a review (PUT upsert — there is no separate create, and calling it again overwrites the previous reply). Only works on verified locations. Returns the ReviewReply {comment, updateTime}. Counts against the 10 edits/min per-profile cap. Reviews live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| delete_review_replyA | Deletes the business's reply to a review (the review itself is the customer's and cannot be deleted). Empty response on success. Reviews live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| list_local_postsA | Lists the local posts (What's New / Event / Offer updates shown on the Business Profile) of a location. Each post has name (accounts//locations//localPosts/{post_id}), summary, topicType, state (LIVE / PROCESSING / REJECTED), searchUrl, createTime and updateTime. Local posts live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| create_local_postA | Publishes a new local post on the Business Profile. Pass the LocalPost as |
| update_local_postA | Updates fields of an existing local post (PATCH with a required updateMask — only masked fields change, e.g. updateMask "summary" with post {"summary": "New text"}). LocalPost fields: languageCode; summary (the post text); topicType (STANDARD | EVENT | OFFER | ALERT); callToAction {actionType: BOOK | ORDER | SHOP | LEARN_MORE | SIGN_UP | CALL, url}; event {title, schedule{startDate{year,month,day}, startTime{hours,minutes}, endDate, endTime}} — required for EVENT and OFFER; offer {couponCode, redeemOnlineUrl, termsConditions}; media [{mediaFormat: "PHOTO", sourceUrl}]. ALERT posts are restricted to Google-initiated campaigns and are typically rejected. Returns the updated post. Counts against the 10 edits/min per-profile cap. Local posts live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| delete_local_postA | Deletes a local post from the Business Profile. Empty response on success. Local posts live only on the legacy v4 API (mybusiness.googleapis.com) — they were never migrated to v1. |
| raw_requestA | Escape hatch to call any Google Business Profile endpoint directly, for endpoints without a dedicated tool. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Tools are cleanly grouped by resource/action: auth setup steps, accounts/locations, reviews, local posts, performance, attributes/categories, and one raw escape hatch. The only close pair, get_daily_metrics vs fetch_multi_daily_metrics, is explicitly differentiated as single-metric vs batched. No two tools appear to do the same thing.
Most names follow a predictable snake_case verb_noun pattern (list_locations, get_location, create_local_post, delete_local_post, update_location_attributes). Minor deviations exist: logout, auth_status, setup_instructions, raw_request, and fetch_multi_daily_metrics versus get_daily_metrics. Still highly readable and mostly consistent.
26 tools is heavy and just over the typical comfortable range, partly because OAuth setup alone uses six tools. The domain is broad enough to justify most of them, but some could potentially be consolidated and the surface sits at the borderline of being unwieldy.
Core workflows are well covered: accounts, locations, reviews and replies, local posts CRUD, performance metrics, attributes, categories, chains, and auth lifecycle. Notable gaps remain for dedicated media/photo operations and location creation/deletion, but raw_request provides a documented escape hatch for uncovered endpoints.