> For the complete documentation index, see [llms.txt](https://docs.moregoodreviews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moregoodreviews.com/agencies/mcp-server.md).

# MCP Server

The **agency MCP Server** connects assistants such as **Claude** to your **white-label agency layer**, the same operations you use to run the reseller side of the product. Through plain-language chat, an authorized assistant can help you manage **customer businesses (projects)**, **clients** who sign in to your branded portal, **agency team members**, **which parts of the console each person may see**, and **extra sidebar links** shown to every client.

This is **not** the same surface as a [single-project MCP connection](/platform/mcp-server.md). Project MCP is where assistants work **inside one business** (customers, review requests, **reviews**, **ratings**, **feedback**, **messages**, **locations**, and related day-to-day reputation work). Agency MCP stays **above** that. It provisions and governs businesses and people, but it does **not** expose per-project review feeds or customer lists.

MCP (**Model Context Protocol**) is the shared standard both connections use. Only the **scope** changes (whole agency versus one project).

{% hint style="info" %}
You need **API access** enabled on your agency account to use this screen. If you see an upgrade prompt, enable API access first, then return to **Agency → MCP Server**.
{% endhint %}

{% hint style="warning" %}
Need to pull **reviews**, **ratings**, or **feedback** for a specific client? Connect the assistant with **project MCP** on that project (or switch connectors), not the agency URL alone. See [**Project MCP Server**](/platform/mcp-server.md).
{% endhint %}

For a complete list of tools the assistant can call, see [**Tools**](/agencies/mcp-server/tools.md).

***

## Open the agency MCP Server page

1. Sign in to your console.
2. Open the **Agency** area from the header (available when you run a white-label agency plan).
3. In the sidebar, choose **MCP Server**.

You will see a short explanation, a field labeled **MCP Server URL** with your agency's address ready to copy, and a link to documentation. If your agency uses a **custom API domain** from [domain setup](/agencies/domain-setup.md), the copied address uses that host so assistants always talk to your branded environment.

Below that, **Connected apps** lists assistants or other tools that have already signed in through this connection. Each tile shows **when** they connected and **what level of access** they were granted. You can **Revoke** any connection you no longer trust.

***

## Connect an assistant

Exact menus change over time, but the pattern matches other MCP integrations.

1. Open your assistant's settings and find **Connectors** or **Integrations**.
2. Choose **Add custom connector** (or the equivalent).
3. Paste the **MCP Server URL** you copied from **Agency → MCP Server**. Use the full address from the copy box, including everything after your API host.
4. Save the connector. The assistant opens a **sign-in** window for your platform account.
5. Complete sign-in, then on the **Authorize** screen choose **your agency** (when you use the copied URL, that choice is usually fixed to the right agency), review the permission levels, and approve.

After authorization, the assistant appears under **Connected apps** on the agency MCP Server page. You can start asking it to help with reseller-level tasks in chat.

{% hint style="success" %}
Reuse the same documentation habits as a [project MCP connection](/platform/mcp-server.md). For example, mention your product name in the first message so the assistant picks the right connector when you use several.
{% endhint %}

{% hint style="warning" %}
An authorized assistant can change **which businesses exist**, **who may access them**, and **sending limits or caps**. Only connect tools you trust, and review confirmations before approving actions that delete a **project**, remove a **client** or **team member**, or otherwise unwind onboarding.
{% endhint %}

***

## What this connection is built for

The agency MCP layer mirrors what the agency console is responsible for at the **reseller** level.

### Customer businesses (projects)

Assistants can help with the lifecycle of each client business under your agency: **listing** them, **creating** new ones, **temporarily suspending** or **restoring** access, **copying** an existing setup into a new business when you need a template, **adjusting plan-style overrides** (such as caps on customers, locations, seats, links, tags, widgets, optional modules like advanced forms or ambassador tools), **tuning email and SMS request limits** so sending stays within what you allow for each client, and **removing** a business when someone is fully offboarded.

### Clients (portal users)

Assistants can **list** people invited as clients, **send invitations** with an appropriate role, **choose which businesses** they may open, **limit which console areas** they see, **resend** a stalled invitation, **update** access after roles or assignments change, and **remove** a client seat.

### Agency team members

Assistants can **list** internal teammates on the agency, **invite** new staff, **resend** invites, and **remove** someone who should no longer have agency-wide access.

### Console sections catalog

Assistants can **look up the catalog of console areas** (stable labels such as reviews, messaging, and similar product surfaces). That list is what you use, often together with client invites, to decide **which slices of the product** a client role is allowed to see.

### External links (client portal sidebar)

Assistants can **list**, **add**, **rename or retarget**, and **remove** the extra shortcuts that appear in your branded client portal sidebar for everyone. For example "Book online" or your marketing site, next to the core product navigation.

***

## Example prompts (agency scope)

These illustrate realistic reseller chores, not reputation analytics inside a single storefront:

* **Projects** — "List every customer business under our agency and note which are suspended." / "Create a project named *Bright Smile Midtown*." / "Duplicate *Demo Bakery* into a new project called *Harbor Cafe*." / "Raise the monthly email request limit on project 42 to match our enterprise tier."
* **Clients** — "Invite *<alex@clientco.example>* as a viewer on projects 3 and 7 with only the sections we use for reporting." / "Resend the pending invite for client membership ID 18."
* **Team** — "Who has agency team seats right now?" / "Invite *<ops@myagency.example>* to the agency team."
* **Sections** — "What console sections exist so I can narrow what our next client invite sees?"
* **Portal links** — "Add a sidebar link *Schedule consult* pointing to our Calendly URL." / "Remove external link ID 5."

When you need **reviews**, **ratings**, **feedback**, or **customer-level** work, switch context to [**project MCP**](/platform/mcp-server.md) for the relevant business.

***

## Permissions at a glance

When you authorize, you typically grant three bands of capability. Your assistant only receives actions that match what you approved:

| Scope      | What it allows                                                                                                                |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Read**   | Inspect projects, clients, team members, the sections catalog, and external links                                             |
| **Write**  | Create or update projects (including limits and overrides), send or adjust invitations and access, and maintain sidebar links |
| **Delete** | Remove projects, client seats, team members, or external links when workflows allow it                                        |

These permissions apply to the **agency you authorized**, not to unrelated spaces or personal accounts.

***

## Disconnect or revoke access

**In the assistant.** Remove or disable the custom connector in that product's settings. Access stops immediately.

**In your agency console.** On **Agency → MCP Server**, under **Connected apps**, choose **Revoke** for a specific tile to invalidate that connection while leaving others intact.

Disconnecting does **not** by itself delete your businesses or portal accounts. It only removes the assistant's ability to act through this agency connection going forward.

If something does not work as expected, see [**Troubleshooting**](/agencies/mcp-server/troubleshooting.md).