Troubleshooting

My AI client can't connect to Agency MCP

Cause: Wrong server URL, missing authorization header, or a stale bearer.

Fix: Verify the following:

• The server URL in your config is exactly https://agency-mcp.launchmaniac.com/mcp — no trailing slash, no /api/mcp, no other variant.
• The Authorization header format is Bearer <your-token> — include the word Bearer followed by a space.
• The bearer token you pasted is current and has not been revoked. Check your dashboard.

I get "401 Unauthorized"

Cause: The bearer token is invalid, expired, or revoked.

Fix: Open your dashboard at https://agency-mcp.launchmaniac.com/app, create a new bearer, and update your AI client's config with the new token. Revoked tokens cannot be reinstated; create a replacement.

I get "429 Too Many Requests"

Cause: You have hit the per-IP rate limit. This can also happen if your network shares a public IP with many other users (e.g., a co-working space or corporate NAT).

Fix: Slow down the request rate. If you are running automated scripts against Agency MCP, add delays between calls. If the issue is a shared IP, you may need to try from a different network. Rate limits reset automatically over time.

I get "payment_required" on tool calls

Cause: Your subscription is paused due to a billing failure. Stripe attempted payment and all retries failed.

Fix: Check your dashboard for a billing alert. Log into Stripe (via the link in your dashboard) to update your payment method or resolve the failed payment. Once the payment succeeds, tool calls resume immediately.

I'm on the Free tier and getting "limit exceeded"

Cause: You have used your 50 tool calls for the current billing month.

Fix: Wait for the next billing cycle to reset the count, or upgrade to the Paid tier for unlimited calls. Upgrading takes effect immediately.

I see "inactive bearer" or "403 Forbidden" on a write tool

Cause: The bearer you are using has its safety mode set to Read-only or No-delete, and the tool you are trying to call requires a higher level.

Fix: Either issue a new bearer with the appropriate safety mode for your use case, or identify a read-only alternative tool. A Read-only bearer cannot perform writes regardless of what the AI requests. See Bearer tokens for guidance on which mode to use.

GHL says "app installed" but the dashboard says "not installed"

Cause: The GHL marketplace OAuth callback may have failed silently during installation, leaving the install incomplete on our side.

Fix: In GHL, go to Settings > Apps, find Agency MCP, and uninstall it. Then reinstall from the marketplace listing. The reinstall re-runs the OAuth handshake and should complete correctly. If the problem persists, contact support.

Tool returns "invalid scope" error

Cause: The tool you are trying to use requires a GHL permission scope that was not granted when you installed Agency MCP. This can happen if the scope list was expanded after your original install.

Fix: Uninstall Agency MCP from the GHL marketplace and reinstall. The reinstall will prompt you to grant the current scope set, which includes any scopes added since your original install.

My AI cannot see a tool I expected, or "permission denied" on a tool the bearer should be able to call

Cause: The bearer has a custom scope subset that excludes the scope this tool needs. Per-bearer scopes are independent of agency-wide scopes — the bearer is restricted even though the agency itself has the permission.

Fix: Open the Permissions tab, pick the bearer, and either enable the missing scope or switch the mode back to "Inherit all granted scopes". Changes apply immediately to the next tool call. See Scope permissions for the full walkthrough.

Something else is wrong

Check the Contact and support page for how to reach us. When contacting support, include the error message, the tool name you were calling, and the rough time the error occurred. That information helps us look up the relevant logs.