QwenWork Integration
QwenWork is Alibaba Cloud's AI workbench with MCP support through its extension connectors.
| Item | Value |
|---|---|
| Config file path | No standalone config file; settings are stored inside the QwenWork app (Extensions → Connectors) |
Configuration Steps
- Open the QwenWork desktop client → Extensions → Connectors
- Click + Add in the top right → Paste JSON config
- Paste the following (recommended — the key travels in a header):
json
{
"mcpServers": {
"shopee-sentinel": {
"type": "streamable-http",
"url": "https://priceminder.online/mcp_server",
"headers": {
"Authorization": "Bearer YOUR_MCP_KEY"
}
}
}
}- Click Import and confirm the connector shows Connected with the 22 tools loaded
- Start a new task before asking anything — connectors only take effect in tasks created after they are enabled; an existing conversation will not pick up the new tools
TIP
QwenWork's MCP transport type is streamable-http (streamable HTTP), which matches PriceMinder's hosted MCP service.
Keep the space after Bearer; without it the credential is rejected.
Alternative: key in the URL
If your build does not accept the headers field, use this form instead (it works, but the key will appear in access logs and screenshots):
json
{
"mcpServers": {
"shopee-sentinel": {
"type": "streamable-http",
"url": "https://priceminder.online/mcp_server?key=YOUR_MCP_KEY"
}
}
}You can also use + Add → manual config: server type Streamable HTTP, paste the URL above, then click + Add Header and enter Authorization / Bearer YOUR_MCP_KEY.
Verification
After configuration, try the following in a QwenWork conversation:
- "My watch list" → Should return monitored product data
- "Any new price drop alerts?" → Should return alert records
FAQ
- Tools not showing: Confirm the connector shows Connected and the MCP key is still valid; connectors only apply to newly created tasks
- Connection failed: Host and path must match as a pair —
priceminder.online/mcp_serverormcp.priceminder.online/mcp.priceminder.online/mcpissues a 301 redirect and the POST request will fail - 401 Unauthorized: The
Authorizationvalue is missing theBearerprefix or its space; or the key is invalid — regenerate it in the panel's MCP center