MCP Server
Connect Claude or other MCP clients to one project for customers, reviews, messages, and reputation tasks.
The MCP Server connects assistants such as Claude to one project at a time so you can work in plain language with customers, review requests, reviews, ratings, feedback, messages, locations, sources, tags, charges, and share templates.
MCP (Model Context Protocol) is a standard way for assistants to use trusted tools. After you connect through sign-in (not by hunting down an API key), the assistant can read and change project records only for the project tied to the URL you paste.
Open Settings → MCP Server in your project and copy MCP Server URL from the box there. That address already includes your project identifier (and your agency's API host when your account runs under a white-label agency). Use it exactly. Do not substitute a generic host-only link.
Running a white-label agency and need assistants to manage clients, team seats, or every business at once? Use Agency MCP Server instead. Project MCP stays inside one customer business.
MCP Server page in Settings
Select the project you want the assistant to use.
Go to Settings → MCP Server.
You will see:
MCP Server URL — copy this full value into your assistant's connector setup.
Connected apps — tiles for tools that already completed sign-in. Each shows access level and recency, and you can Revoke access here when needed.
Example prompts — starter instructions you can paste into chat once the connector is live.
For a complete list of tools the assistant can call, see Tools.
What assistants can help with
Capabilities mirror what your project supports today. They focus on this business, not your agency console.
Customers
Look up people in your directory; add or remove records; update notes and contact preferences; attach tags; archive or restore; stop or resume outreach where supported; cancel queued-but-not-sent messages; inspect related charges, messages, or reviews for one person when reconciling history.
Review requests
Schedule review requests (email or SMS according to your strategy, reminders, eligibility, and sending limits). Integrations do not bypass your throttles or unsubscribe rules.
Reviews
Search and read feedback already collected; create reviews manually (finding or creating the customer by email or phone); adjust moderation flags such as hidden or duplicate when cleaning data; attach tags to reviews; mark reviews as replied when you handled the response outside the connector; publish replies to Google or Facebook when those integrations are connected; remove reviews when upstream reconciliation requires it; generate share images using your saved share templates.
To publish replies through connected Google or Facebook integrations, the assistant uses the Reply to Review on Integration tool after you confirm each draft. For built-in AI reply flows inside the product UI, see AI Assistant.
Messages
Review outbound history for reporting-style questions (for example delivery-oriented summaries over recent campaigns). Individual messages can be removed when an integration needs to tidy audit data. New review requests are created through asks, not by inventing arbitrary message rows.
Locations
List, add, edit, or remove locations so attribution stays aligned when assistants help import or reorganize multi-site data.
Charges
Record or delete spend signals tied to customers when you sync billing or point-of-sale events into the project.
Sources and tags
Maintain the sources catalog your reviews roll up under and the tags you use across customers and reviews.
When an assistant sets a preset icon on a source or tag (not a custom uploaded image), use two lowercase words separated by one space, such as fab fa-google or fas fa-star. Omit the icon when you rely on an uploaded image instead.
Share templates
List saved layouts for social-style review graphics or remove templates that are no longer needed.
Connect Claude or another MCP assistant
Menus vary by product, but the flow is consistent:
Open the assistant's Settings.
Open Connectors, Integrations, or the equivalent.
Choose Add custom connector (or similar).
Paste the MCP Server URL from Settings → MCP Server. Use the entire string from the copy box.
Save. The assistant opens a sign-in window linked to your account.
Sign in if prompted. On Authorize, pick the project when asked (if your connector URL already scopes one project, that choice may be fixed for you), review read, write, and delete style permissions, and approve.
When the connector shows as connected, try one of the Example prompts from your MCP Server page or any of the suggestions below.
To move the assistant to a different project, remove the connector and add it again using that project's MCP Server URL, then authorize again.
Example prompts
These match the built-in Example prompts block on your MCP Server page:
Weekly review digest — Ask for a concise summary of reviews from the last seven days with counts, averages, breakdown by source and location, recurring praise, and recurring concerns.
Send review requests safely — Ask the assistant to list customers who match your criteria (for example recent sign-ups who have never been asked) and wait for your confirmation before scheduling sends with reminders.
Add someone and ask — Provide contact details for a new customer, then have the assistant create the record and schedule the first review request with your preferred reminder count.
Who still needs an ask — Request a capped list (for example up to 50) of customers never asked, newest first, skipping unsubscribed contacts, with name, email, and signup date.
Location comparison — Ask for a ninety-day leaderboard by location using review volume, average rating, share of five-star scores, and a simple trend versus the prior ninety days.
Outreach health — Ask for counts and rates across recent email sends (totals, delivery, opens, clicks, failures) so you can spot anomalies over roughly the last two weeks.
Your assistant still reasons in natural language. It chains the underlying lookups and updates for you.
Assistants often pause for confirmation before bulk sends, large deletes, or anything similarly impactful. Use that moment to double-check filters and counts.
The server also ships built-in workflow prompts (Reputation Dashboard, Review Velocity, Triage Negative Reviews, and others). See Tools for the full list.
Permissions
Authorization typically exposes three bands of capability. The assistant only sees actions allowed by what you approve:
Read
Inspect customers, reviews, messages, locations, charges, sources, tags, and share templates
Write
Create or update customers and locations; schedule review requests; record charges; maintain sources and tags; adjust review flags, tags, mark-as-replied, integration replies, or share-image jobs
Delete
Remove customers, reviews, messages, locations, charges, sources, tags, or templates when those workflows are permitted
Everything stays inside the one project you authorized. Other projects, billing screens, and agency-wide controls remain out of scope unless you add a separate connector.
Treat MCP access like handing someone your project keyboard. Prefer assistants you trust, and review destructive actions (deletes, bulk outreach, broad flag changes) before approving them.
Other MCP-compatible assistants
Any client that supports custom MCP connectors can use the same copied URL and the same sign-in flow, not only Claude. Cursor, Claude Desktop, and other MCP clients follow the same pattern.
Disconnect or revoke
Inside the assistant. Remove the connector from its settings list. Access stops immediately.
Inside More Good Reviews. On Settings → MCP Server, use Revoke under Connected apps for fine-grained cleanup, or revoke tokens from your account security flows if you suspect misuse.
Disconnecting does not erase reviews, customers, or ratings. It only removes the assistant's path back into the project. Reconnect any time by repeating authorization with the same MCP Server URL.
Tips
Name the product and project in your first message ("In More Good Reviews for Bright Dental, …") so the model reliably chooses this connector when several are installed.
Save recurring prompts (weekly digests, monthly "never asked" sweeps, outreach audits) as reusable snippets inside your assistant.
Assistants may hit practical limits when reading huge histories in one pass. Narrow time ranges ("last 30 days") or row counts ("latest 100 reviews") when results truncate unexpectedly.
If something does not work as expected, see Troubleshooting.
Last updated