Shade Browser MCP

Troubleshooting

Fix common MCP connection, API key, and slot quota failures.

Troubleshooting

MCP add command fails

Check that your client supports streamable HTTP MCP servers. Claude Code uses --transport http; Codex uses --url. Other clients may use a config file with URL, transport, and headers fields.

API key returns 401

Confirm the header is exactly:

Authorization: Bearer YOUR_KEY

Create a fresh key in the dashboard if the key was revoked, copied with extra spaces, or never activated for the account.

No free slots

Slot quota errors mean all slots on your plan are currently claimed or a prior agent run did not release its slot. List current slots, release idle work, then retry:

browser_list_slots
browser_release_slot(slot: IDLE_SLOT)
browser_claim_slot

Session does not restore cleanly

Some sites rotate short-lived challenge or device cookies. Try loading the session while dropping those cookies:

browser_load_session(name: "your-session", drop_cookie_names: "cf_clearance")

Cloudflare or Turnstile challenge appears

Leave SHADE_PERSONALITY off unless you are deliberately testing personality behavior. The default real Brave fingerprint is more reliable for challenge pages than an injected personality profile.