Google Business Profile MCP vs Klaviyo MCP
A side-by-side look at the Google Business Profile MCP and Klaviyo MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Business Profile MCP for monitoring work as a local process; choose Klaviyo MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Business Profile MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_BUSINESS_CLIENT_ID, GOOGLE_BUSINESS_CLIENT_SECRET, GOOGLE_BUSINESS_REFRESH_TOKEN. - You want tools like
auth_status, setup_instructions, set_client.
Choose Klaviyo MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_accounts, list_campaigns, campaign_report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 63/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_BUSINESS_CLIENT_IDGOOGLE_BUSINESS_CLIENT_SECRETGOOGLE_BUSINESS_REFRESH_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 26 | 24 |
| Full listing | View Google Business Profile MCP | View Klaviyo MCP |
Tools & capabilities
Google Business Profile MCP tools 26
auth_statusShows 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_instructionsStep-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_clientSaves 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_loginFirst 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_loginSecond step: confirms the browser consent finished, 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.logoutRevokes 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_accountsLists 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_locationsLists 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_locationReturns 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_locationUpdates fields of a location (PATCH with a required updateMask — only masked fields change). Pass the new values in `location`, e.g. {"title": "New name"} with updateMask "title". Set validateOnly to check the change without applying it. Note: every profile has a hard cap of 10 edits per minute (not raisable) — batch your changes into one call where possible. Returns the updated Location.list_categoriesLists/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_metadataLists 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).- +14 more on the listing page
Klaviyo MCP tools 24
list_accountsList all configured Klaviyo accounts. Use this first to see which brands are available.list_campaignsList recent email campaigns for a specific Klaviyo account. Returns campaign IDs, names, status, and send dates.campaign_reportGet email campaign performance metrics for a Klaviyo account. Returns opens, clicks, revenue, bounce rate, unsubscribes for the specified time period.list_metricsList available metrics for a Klaviyo account. Use this to find the 'Placed Order' metric ID needed for revenue reporting.multi_account_summaryPull campaign performance summary from ALL configured Klaviyo accounts. Returns a unified cross-brand report.flow_reportGet email flow (automation) performance for a Klaviyo account. Returns metrics for welcome series, abandoned cart, post-purchase, etc.campaign_ab_reportGet per-variation (A/B arm) email/SMS campaign metrics for a Klaviyo account. Splits results by variation so you can compare arms.flow_series_reportTime-series flow (automation) metrics for a Klaviyo account. Buckets by interval.segment_reportSegment performance metrics for a Klaviyo account: member counts, additions, removals.form_reportSign-up form performance for a Klaviyo account: views, submissions, submit rate.list_segmentsList all segments in a Klaviyo account with name, member count, and creation date.list_listsList all email lists in a Klaviyo account with name, opt-in process, and creation date.- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Business Profile MCP
{
"mcpServers": {
"google-business-profile-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-google-business@latest"
],
"env": {
"GOOGLE_BUSINESS_CLIENT_ID": "YOUR_GOOGLE_BUSINESS_CLIENT_ID_HERE",
"GOOGLE_BUSINESS_CLIENT_SECRET": "YOUR_GOOGLE_BUSINESS_CLIENT_SECRET_HERE",
"GOOGLE_BUSINESS_REFRESH_TOKEN": "YOUR_GOOGLE_BUSINESS_REFRESH_TOKEN_HERE"
}
}
}
}
Klaviyo MCP
{
"mcpServers": {
"klaviyo-mcp": {
"command": "npx",
"args": [
"-y",
"@scalably-io/klaviyo-mcp"
]
}
}
}
Frequently asked questions
Google Business Profile MCP is categorized under Monitoring and uses a local stdio subprocess. Klaviyo MCP belongs to Monitoring and uses a local stdio subprocess. Pick Google Business Profile MCP for monitoring work and Klaviyo MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google Business Profile MCP has no declared pricing — check the project's own site. Klaviyo MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-business-profile-mcp and klaviyo-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Business Profile MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 4 GitHub stars. Klaviyo MCP has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.