> 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/troubleshooting.md).

# Troubleshooting

This guide covers common issues when connecting an MCP assistant to your **agency** in More Good Reviews. Most problems come down to the **URL you paste**, **permissions you approve**, or **API access** not being enabled on your plan.

{% hint style="info" %}
For project-level MCP issues (customers, reviews, messages inside one business), see [**Project MCP Troubleshooting**](/platform/mcp-server/troubleshooting.md).
{% endhint %}

***

## The assistant cannot connect at all

### Use the full MCP Server URL

Copy **MCP Server URL** from **Agency → MCP Server**. Paste the **entire** string into your assistant's connector setup.

{% hint style="warning" %}
Do **not** paste a generic API host or invent a path. The agency URL includes a scoped segment and looks similar to `https://api.example.com/mcp/a/…`.
{% endhint %}

### Custom API domain

If your agency uses a **custom API domain** from [domain setup](/agencies/domain-setup.md), the copied URL uses that host. Always paste the value from **your** console, not a generic More Good Reviews example.

### Re-add the connector after URL changes

If you changed domains, remove the old connector and add a new one with the current **MCP Server URL**, then authorize again.

***

## Sign-in or authorization fails

### Complete the flow in one session

When you save a new connector, the assistant opens a **sign-in** window. Finish sign-in and click **Authorize** before the window closes. If you see a message that the authorization request is missing or expired, start again from **Add custom connector**.

### Choose the correct account

Sign in with the MGR account that owns the agency. Client portal users may not have permission to authorize MCP connections.

### Agency MCP requires API access

On **Agency → MCP Server**, if the page is locked behind an upgrade prompt, enable **API access** on your agency plan first, then return to MCP setup.

### Grant enough scope

If you only approved **Read**, the assistant cannot invite clients, create projects, or delete records. Remove the connector, reconnect, and approve **Write** or **Delete** when you need those actions.

| Symptom                                           | Likely cause             | Fix                                             |
| ------------------------------------------------- | ------------------------ | ----------------------------------------------- |
| Assistant says it cannot create or update records | Read-only authorization  | Reconnect and approve **Write**                 |
| Assistant cannot delete records                   | Delete scope not granted | Reconnect and approve **Delete**                |
| Fewer tools than expected                         | Partial scopes           | Reconnect and review all three scope checkboxes |

***

## Connected but the wrong data appears

### Agency versus project server

Agency MCP manages **businesses, portal clients, and team members** at the reseller level. It does **not** return review feeds or customer lists for a client storefront. For that work, connect [**Project MCP Server**](/platform/mcp-server.md) on the relevant project.

### Name the connector in chat

When you run several MCP connectors, start your message with your product or agency name so the assistant selects the right one.

***

## Results look incomplete or truncated

### Large lists are paginated

Project lists, client directories, and team rosters may span many pages. Ask the assistant to request the next page or narrow the query.

***

## Connected apps do not show the assistant

After authorization, the assistant should appear under **Connected apps** on **Agency → MCP Server**.

1. Confirm authorization finished with a success message.
2. Refresh the settings page.
3. If it still does not appear, revoke any stale entry, remove the connector in the assistant, and connect again.

Each tile shows **scopes** (read, write, delete) and **when** the connection was approved. Use **Revoke** on a tile to cut off one assistant without affecting others.

***

## Actions fail or return errors

### Duplicate or suspended projects

**Duplicate Project** needs a source project ID and a new name. **Suspend Project** blocks client access until you **Unsuspend Project**.

### Client invites and sections

When inviting clients with section restrictions, ask the assistant to call **List Sections** first so it uses valid section identifiers from your agency catalog.

***

## Disconnect and start fresh

**In the assistant.** Remove or disable the custom MCP connector.

**In MGR.** On **Agency → MCP Server**, click **Revoke** on the relevant **Connected apps** tile.

Disconnecting does **not** delete your businesses or portal accounts. It only removes the assistant's access. Reconnect anytime with the same URL and a new authorization.

***

## Still stuck?

1. Verify you copied the latest **MCP Server URL** from **Agency → MCP Server**.
2. Confirm **API access** is enabled on your agency plan.
3. Re-authorize with the scopes you need.
4. Try a simple read-only prompt first ("List agency projects") before write or delete tasks.

For tool names and permissions, see [**Tools**](/agencies/mcp-server/tools.md). For setup walkthroughs, see [**MCP Server**](/agencies/mcp-server.md).