[bug] search web MCP 405 Method Not Allowed - current mcp not support streamableHttp

[chenggb123]

Environment

• CLI: bl 1.14.0
• Skill: 1.14.0
• Node: v24.18.0
• OS: Windows 10
• Region: cn (domestic, cn-beijing)

Reproduce

bl search web --query "test" --count 1
# or
bl mcp tools --server WebSearch
# or
bl mcp tools --server QwenImage

Expected

bl search web should return web search results using the DashScope MCP WebSearch service; bl mcp tools should list tools exposed by the MCP server.

Actual

All MCP-backed commands fail with HTTP 405:

Error: MCP request failed: 405 Method Not Allowed - current mcp not support streamableHttp
Exit code: 1

With --verbose:

> POST https://dashscope.aliyuncs.com/api/v1/mcps/WebSearch/mcp
> Method: initialize
< 405 Method Not Allowed

Notably, bl mcp list (console gateway, non-MCP) works and shows the MCP servers with installType: "StreamableHttp" but streamable: false — e.g. WebSearch, QwenImage, WebParser (SSE). The CLI appears to connect with the streamableHttp transport regardless, while the server rejects it with current mcp not support streamableHttp.

JSON error (if any)

{
 "error": {
 "code": 1,
 "message": "MCP request failed: 405 Method Not Allowed - current mcp not support streamableHttp"
 }
}

Already tried

• bl update ran (auto-updated 1.10.1 → 1.14.0) and skill version aligned with CLI (1.14.0)
• bl auth status OK (API key + console domestic logged in)
• Console re-login (bl auth login --console --console-site domestic) — still reproduces
• Retried with --verbose — same failure

Notes

• Frequency: always (every MCP-backed command, every attempt)
• Invoked via: terminal
• bl mcp list succeeds (console gateway) — only the MCP endpoint connection (/api/v1/mcps/<code>/mcp) fails with 405
• No request_id in verbose output

[hopelynd]

Hi, thanks for the detailed report.

This is expected with the current CLI behavior: bl only speaks Streamable HTTP for MCP (POST .../api/v1/mcps/<code>/mcp). It does not fall back to legacy SSE / UVX.

Your bl mcp list output is consistent with that: servers like WebSearch / QwenImage show installType: "StreamableHttp" but streamable: false, so the instance is still on the old transport. The server then rejects Streamable HTTP with:

405 Method Not Allowed - current mcp not support streamableHttp

Workaround (usually fixes it):

1. Open the MCP marketplace page for the affected server (e.g. WebSearch):
   https://bailian.console.aliyun.com/?tab=mcp#/mcp-market/detail/WebSearch
2. Deactivate / cancel, then activate again (so the instance upgrades to real Streamable HTTP).
3. Retry:

bl search web --query "test" --count 1
# or
bl mcp tools --server WebSearch

Please do the same for any other MCP that fails the same way (e.g. QwenImage).

If it still fails after re-activation, paste a fresh bl mcp list --output json snippet for that server (code / installType / streamable) and we can dig further.

We’ll also look at improving the CLI error/hint for this 405 case (today the “re-activate for Streamable HTTP” guidance mainly covers the 404 not activated path).

[XXPermanentXX]

Hi, since we haven’t received any further feedback, we’ll close this issue for now.

If the issue still occurs after deactivating and reactivating the affected MCP, please leave a comment with the latest bl mcp list --output json output, and we’ll take another look.

Thanks!