# MCP troubleshooting

Fix connection, permission, approval, validation, rate-limit, and media problems in an MCP client.

## No Beacon tools appear

Confirm that the server address is exactly `https://postwithbeacon.com/mcp`.

Complete browser sign-in. Then refresh or restart the client connection.

## Sign-in repeats

Do not add an API key. Run the MCP login or authentication command again.

Beacon access is valid only for the exact `/mcp` resource.

## A permission error appears

Reconnect Beacon. Select the correct account, workspace, and permissions.

Confirm that the user still belongs to the workspace. Hosted MCP also requires an active Beacon plan; Free is eligible.

## Publication needs approval

Beacon returns `APPROVAL_REQUIRED` for immediate publication.

Open the returned Beacon URL. Approve the exact post, then retry the unchanged request.

## A post is not ready

Run `beacon_check_post`. Fix the reported field, text limit, media rule, scheduled time, or channel connection.

## Beacon limits requests

A `429` result means too many requests reached Beacon. Wait for the `Retry-After` duration.

Then follow the selected tool retry rule.

## Local media is unavailable

Search for upload media. Call `beacon_get_media_upload_link`.

Let the user upload through Beacon. Then list and inspect the new media item.

## The result stays unclear

Read the request ID and safe error details. Do not repeat an uncertain publication automatically.

Check Beacon and the provider. Contact support if the final result remains unknown.