Doubao Integration

Doubao (ByteDance) supports MCP through custom connectors. Configuration is a form, not a pasted JSON block.

Item	Value
Config file path	No standalone file — settings live inside the Doubao desktop client (custom connector form)
Client requirement	Desktop client only; the web version has no custom connector entry

Configuration Steps

1. Open the Doubao desktop client → sidebar "Plugins · Skills · Partners" (插件 · 技能 · 伙伴)
2. Top-right "+ Add" on the plugins page → "New custom connector"
3. Fill in the form:

Field	Value
Server name	PriceMinder
Transport type	HTTP
Server URL	https://priceminder.online/mcp_server
Custom Headers	name Authorization, value Bearer YOUR_MCP_KEY

Three easy mistakes

1. Keep the space after Bearer — write Bearer abc-123. A missing space is treated as an invalid credential.
2. Bearer is a plain ASCII word; full-width or localized characters will not work.
3. Write the address through the /mcp_server path segment. A bare host without a path fails in most clients, and priceminder.online/mcp issues a 301 redirect that breaks the request.

4. After saving, a "PriceMinder" plugin card appears on the home page. Open it to see the 22 tools, then click "Try in chat" at the bottom right to verify.

Why pass the key in a header

Putting the key in the URL (...?key=xxx) also works, but the key then shows up verbatim in access logs, browser history and screenshots. A header travels only with the request and never lands in a logged URL field, so the exposure surface is far smaller. The server accepts both; use headers for any new configuration.

Alternative: key in the URL

If your Doubao build has no "Custom Headers" row, put the key in the address instead:

Field	Value
Server URL	https://priceminder.online/mcp_server?key=YOUR_MCP_KEY
Custom Headers	leave empty

This works immediately, but avoid posting screenshots that contain the full URL with the key.

Verification

After configuration, try the following in a Doubao conversation:

• "My watch list" → should return monitored product data
• "Any new price drop alerts?" → should return alert records

Real data coming back means the key passed validation and the connector is working.

FAQ

• 401 Unauthorized: the Authorization value is missing the Bearer prefix or the space after it; alternatively the key expired — regenerate it in the panel's MCP center
• Tools not showing: confirm the connector is enabled; some builds only refresh the tool list after toggling the plugin off and on
• No entry in the web version: custom connectors are desktop-only
• Wrong URL: it must be the /mcp_server path on the priceminder.online host; priceminder.online/mcp issues a 301 redirect and the POST request will fail
• Rotated the key: just update the Authorization value in the connector settings — no need to delete and recreate it