My AI assistant can analyze every client account, but I still set each one up by hand
The AI Hub is great for reading: with Claude I can review a client's reviews, campaigns, contacts and metrics in minutes, and draft replies or Google Posts that wait for approval. But as soon as a client needs setting up or changing (a new location, a campaign, its texts, a review source, the reply prompt), the assistant has no tool for it. So I end up driving the dashboard with an AI that clicks through the browser, which is slow and fragile, or doing it myself.
In my done-for-you work, this is where most of the time goes: onboarding a client and keeping its setup right. The guardrails are already there (scoped tokens, write permission, approval queue, audit log), which is exactly what makes it safe to go further.
What happens today
MCP: 57 tools to read data, draft review replies, tag reviews, run Local Search Grid scans, prepare Google Posts and manage SMS providers.
REST API: can also create and update customers, organizations and locations, issue Google or Facebook connect links and send review invites. None of these are available as MCP tools.
Neither the MCP nor the API can create or edit a campaign (steps, email and SMS texts, delays, sending window, logo), pause or resume it, import a contact list (the API sends invites one at a time), add a review source other than Google or Facebook, change the review form and page, set the AI reply prompt or auto-respond rules, or invite a user with a role. Blueprints help with a first setup, but the assistant can't apply one or adjust what comes after.
Driving the dashboard instead: the active organization is shared across tabs and sessions, so a change in one place switches the client everywhere else (reported here: https://roadmap.embedmyreviews.com/en/p/switching-client-in-one-tab-silently-switches-every-other-tab). During one of those switches, a save I had made was lost without any message.
Proposal (simplest first)
Bring to the MCP what the REST API already does: create and update organizations and locations, issue connect links, send invites.
Campaign setup tools: apply a blueprint package to an organization, create a campaign from a blueprint, edit its steps (texts, sender, logo, delays), schedule, pause and resume, and import contacts into a paused campaign. Same approval and audit rules as Google Posts.
Account settings tools: review sources (custom and third-party URLs), review form and page texts, AI reply prompt per organization, auto-respond rules, user invitations with a role.
Make every write tool explicit and safe for agents: an explicit organization_id on every write call, never tied to the dashboard's active organization; a preview (dry run) before saving; the saved state returned after saving; everything in the audit log.
The dashboard side (one client per tab) is covered in the request linked above.
What it would change: onboarding a client becomes a conversation with an assistant that prepares everything, with a person approving what goes live; fewer setup mistakes across many clients; and setup no longer depends on knowing every screen of the dashboard.
Related: Use the organization name as the default location name, where another agency mentions managing clients through the MCP.
Log in to comment and vote
No comments yet
Be the first to share your thoughts.