Troubleshooting
Fix agency MCP connection, authorization, missing tools, and scope issues.
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.
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.
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/….
Do not substitute a custom API domain
Agency MCP Server URL uses the platform API host, even if you set a White Label API domain under domain setup. Always paste the value from Agency → MCP Server, not a host you invent from your branded API domain.
Re-add the connector after URL changes
If the MCP Server URL in your console changed, remove the old connector and add a new one with the current 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.
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
Assistant cannot roll a project secret key
Delete scope not granted
Reconnect and approve Delete. Rolling a key is a delete action.
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 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.
Confirm authorization finished with a success message.
Refresh the settings page.
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?
Verify you copied the latest MCP Server URL from Agency → MCP Server.
Confirm API access is enabled on your agency plan.
Re-authorize with the scopes you need.
Try a simple read-only prompt first ("List agency projects") before write or delete tasks.
For tool names and permissions, see Tools. For setup walkthroughs, see MCP Server.
Last updated
Was this helpful?