Bright Data MCP with OpenAI: use SSE, not Streamable HTTP

If the Bright Data MCP fails specifically against OpenAI endpoints: 1. Check which transport you configured. The Streamable HTTP path (/mcp) is the one that breaks with OpenAI; switch to the SSE version. 2. Follow the OpenAI example in the Bright Data docs, which uses the SSE path. 3. Do not assume a transport that works with other clients (Claude, etc.) works with OpenAI; match the transport to the client per the docs.

Context: GitHub issue (brightdata/brightdata-mcp#44, closed): connecting the Bright Data MCP to the OpenAI Responses API failed. The maintainer diagnosed it immediately: the reporter was using the Streamable HTTP version, which is problematic with OpenAI endpoints. Switching to the SSE version resolved it, and the reporter confirmed. The docs example for OpenAI uses the SSE path; the /mcp Streamable HTTP path works with most other clients.

Source: GitHub issue (brightdata/brightdata-mcp#44, closed): connecting the Bright Data MCP to the OpenAI Responses API failed. The maintainer diagnosed it immediately: the reporter was using the Streamable HTTP version, which is problematic with OpenAI endpoints. Switching to the SSE version resolved it, and the reporter confirmed. The docs example for OpenAI uses the SSE path; the /mcp Streamable HTTP path works with most other clients.

Verified resolution: If the Bright Data MCP fails specifically against OpenAI endpoints: 1. Check which transport you configured. The Streamable HTTP path (/mcp) is the one that breaks with OpenAI; switch to the SSE version. 2. Follow the OpenAI example in the Bright Data docs, which uses the SSE path. 3. Do not assume a transport that works with other clients (Claude, etc.) works with OpenAI; match the transport to the client per the docs.

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