---
title: "MCP Troubleshooting | Rendley MCP Docs"
description: "Fix the common Rendley MCP problems, such as the server not appearing, auth failures, tool calls timing out and stale client caches."
url: https://docs.rendley.com/mcp/troubleshooting/
---

# Troubleshooting

The issues you are most likely to hit, grouped by what you see.

## Authentication

### `401 Unauthorized`

The key or session is missing, malformed, or revoked.

- Check the header reads exactly `Authorization: Bearer ABC123...`, one space, no quotes around the key.
- If the key is in an env var, confirm it is exported in the same shell that launched the client (`echo $RENDLEY_API_KEY`).
- Test the key directly:   ``` curl -i https://mcp.rendley.com/health/details \
 -H "Authorization: Bearer $RENDLEY_API_KEY" ```   `200` means the key works and the problem is in the client config. `401` means the key itself is rejected.   Use `/health/details`, not `/health`. The plain health check takes no auth and answers `200` even with a bad key, so it cannot tell you whether your key is valid.
- If you rotated the key, the old one fails immediately. Update the client and reconnect.

### Sign-in fails or “authorization required” stays

The browser redirect did not complete.

- Allow pop-ups for `app.rendley.com` and retry.
- On a corporate network, ask IT to allowlist `*.rendley.com`. A proxy or VPN can strip the redirect.
- For the Codex CLI, a firewall may block the local callback port. Use an API key instead.

## Connection

### The client does not see the tools

The server is registered but not active for this conversation.

- **Claude desktop**: fully quit the app (including the menu-bar icon) after editing the config, then reopen.
- **Codex desktop**: open Settings → MCP servers and confirm `rendley` is saved and enabled.
- **Perplexity**: start a new thread. Connectors attach when a thread is created.
- **Claude Code / Codex CLI**: run `/mcp` or `codex mcp list` to confirm the server is connected.

### “Server is not running” or a red dot

The URL is wrong or the network cannot reach the server.

- Open `https://mcp.rendley.com/health` in a browser. You should see `{"agent_runtime":"api-jobs","status":"ok"}`. This endpoint needs no auth, so it only proves the server is reachable.
- Confirm the URL is `https://mcp.rendley.com/mcp/automation` with no trailing slash. Use `https://mcp.rendley.com/mcp` only when you intentionally want the lighter project-preparation connector.
- On a corporate network, ask IT to allow `mcp.rendley.com` over HTTPS.

## Edits and exports

### The edit comes back “in progress”

The edit ran past the time budget. Ask the client to continue, and it resumes the same session. No work is lost.

### “Needs upgrade”

You hit a plan limit (projects, storage, transcription, brand kit). Check your plan in [Settings](https://app.rendley.com/settings?utm_source=docs.rendley.com&utm_medium=docs&utm_campaign=mcp&utm_content=content_link), or free up usage.

If the plan cannot be read at all, the tool answers “Could not verify your plan right now.” Retry in a moment.

### An edit fails

The error message names the cause. The most common is a transient **browser session crash**. Retry and it usually clears. If it repeats on the same input, [tell us](mailto:support@rendley.com).

### A tool says the plan does not allow it

Editing and exporting require a paid plan. Connecting, checking your account and browsing projects do not. Check your plan in [Settings](https://app.rendley.com/settings?utm_source=docs.rendley.com&utm_medium=docs&utm_campaign=mcp&utm_content=content_link).

### Export takes a while

Long renders take a few minutes. Ask the client to check the export and it reports back when the file is ready.

## Still stuck?

- [Authentication](https://docs.rendley.com/mcp/authentication/) covers the sign-in and key flows in detail.
- [support@rendley.com](mailto:support@rendley.com). Include the client name, the failing request, and the full error.

## What to read next

- **[Introduction](https://docs.rendley.com/mcp/getting-started/)** shows the complete file-to-video workflow.
- **[Connect your AI client](https://docs.rendley.com/mcp/connect/)** is the setup for Claude, ChatGPT, Codex and other clients.
- **[Authentication](https://docs.rendley.com/api/authentication/)** covers API keys, bearer tokens and the errors they cause.

[Previous pageThe Claude directory version](https://docs.rendley.com/mcp/public-connector/) [Next pageJavaScript Video Editing SDK](https://docs.rendley.com/sdk/introduction/)
