Bright Data MCP: empty results with success means check the account

Bright Data MCP: empty results with success means check the account

TL;DR

When the remote MCP returns empty results with a success status: 1. Do not debug your client code first; the STDIO and remote versions share the same scrape-as-markdown code path, so a client-side bug would break both. Check the account itself: in this case the account had been disabled by a platform-side bug.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

2. 3. Share your account ID or signup email with support so they can check internally; the maintainer resolved this one within the thread once they looked at the account. 4. Confirm the fix by rerunning the exact same query that returned empty results.

Context: GitHub issue (brightdata/brightdata-mcp#106, closed): the remote MCP at mcp.brightdata.com returned empty results while the event logs showed success. The maintainer investigated a reporter's account, found a bug on Bright Data's end that had disabled the account, re-activated it, tested, and the reporter confirmed everything worked. Same code path serves both the remote MCP and the STDIO version, so the empty results were never a client bug.

Source: GitHub issue (brightdata/brightdata-mcp#106, closed): the remote MCP at mcp.brightdata.com returned empty results while the event logs showed success. The maintainer investigated a reporter's account, found a bug on Bright Data's end that had disabled the account, re-activated it, tested, and the reporter confirmed everything worked. Same code path serves both the remote MCP and the STDIO version, so the empty results were never a client bug.

Verified resolution: When the remote MCP returns empty results with a success status: 1. Do not debug your client code first; the STDIO and remote versions share the same scrape-as-markdown code path, so a client-side bug would break both. 2. Check the account itself: in this case the account had been disabled by a platform-side bug. 3. Share your account ID or signup email with support so they can check internally; the maintainer resolved this one within the thread once they looked at the account. 4. Confirm the fix by rerunning the exact same query that returned empty results.

Source URL: https://github.com/brightdata/brightdata-mcp/issues/106