Skip to main content

Documentation Index

Fetch the complete documentation index at: https://rendobar.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Known failures with the local stdio server (@rendobar/mcp) and the fixes. Errors are quoted from the actual stderr the server emits.

​
”No Rendobar API key found”

The server didn’t see a key in any of the three sources. 
No Rendobar API key found. Provide one via:
  1. --api-key=<key> command-line flag
  2. RENDOBAR_API_KEY environment variable
  3. credentials file at ~/.config/rendobar/credentials.json
Cause: the env block in your client config didn’t get applied, or the key has the wrong prefix (must start with rb_). Fix: verify the config file your client actually loaded. In Claude Desktop, Settings → Developer → Open MCP Log Folder shows the launch command and the env vars it received. If RENDOBAR_API_KEY is missing there, the config file path is wrong.

​
”Invalid Rendobar API key”

Invalid Rendobar API key: must start with 'rb_' (got 'sk_li...')
The key was read but doesn’t look like a Rendobar key. You probably pasted an OpenAI or Stripe key. Get a Rendobar key at app.rendobar.com → Settings → API Keys.

​
”@rendobar/mcp requires Node.js 20 or later”

Node check at boot failed. Fix: upgrade Node to 20.10 or later, or use nvm / fnm / volta to install side by side.

​
Cursor on macOS can’t find npx

Cursor launched from the macOS Dock inherits the GUI environment, not your shell PATH. If you installed Node via nvm or asdf, npx isn’t on the GUI PATH. Fix: use the absolute path to npx in ~/.cursor/mcp.json: 
{
  "mcpServers": {
    "rendobar": {
      "command": "/Users/you/.nvm/versions/node/v20.18.0/bin/npx",
      "args": ["-y", "@rendobar/mcp"],
      "env": { "RENDOBAR_API_KEY": "rb_live_..." }
    }
  }
}
Find the path with which npx in your terminal.

​
Windows: ‘npx’ is not recognized

Some clients on Windows don’t auto-resolve npx to npx.cmd. Fix: use "command": "npx.cmd" in the config block.

​
Tool calls hang

Almost always means the server crashed silently after the handshake. Check stderr:
  • Claude Desktop: Settings → Developer → Open MCP Log Folder → mcp-server-rendobar.log
  • Cursor: Output panel → MCP
  • VS Code: Output panel → MCP → rendobar
  • Cline: Cline output panel
Look for JSON lines with "level": "error". The errCode field maps to a specific failure (see Errors).

​
“exceeds plan limit”

File size (250000000 bytes) exceeds plan limit (104857600 bytes). Upgrade your plan for larger uploads.
Free plan caps uploads at 100 MB. Pro plan caps at 2 GB. Either compress the file before upload or upgrade. Check your current limit by asking the agent: “What’s my Rendobar max upload size?” — it calls get_account.

​
Server boots but agent reports no tools

The handshake succeeded but tools/list returned empty. This is rare — usually means the package version is corrupt. Fix: clear the npx cache and reinstall: 
npm cache clean --force
npx -y @rendobar/mcp@latest --version
You should see a version string like 1.0.1. If not, file an issue.

​
Agent uploaded the wrong file

upload_file resolves relative paths against the working directory of the MCP server process — usually your home directory or the directory the IDE was launched from. Always use absolute paths in your prompts to be unambiguous.

​
See also