Connect WorkBuddy to Wenbo MCP

1. Prepare the extension and a dedicated key

1. Install the Wenbo extension, sign in to Wenbo and your target platforms, and keep the browser online.
2. Create a dedicated MCP key in the console, named WorkBuddy so you can manage it separately.
3. Store the key in the client’s local credentials or WENBO_MCP_KEY environment variable. Never send it in an AI chat.

2. Configure the remote MCP service

Service URL: https://mcp.wenbodesk.com/mcp；mcp-key is the authentication header.

Use a custom connector supporting a user-provided token. The existing integration guide requires WorkBuddy 4.23.0+ and connector metadata with auth_mode: token and a credentials form that injects the token into mcp-key.

{
  "mcpServers": {
    "wenbo": {
      "type": "streamableHttp",
      "url": "https://mcp.wenbodesk.com/mcp",
      "headers": {
        "mcp-key": "${WENBO_MCP_KEY}"
      }
    }
  }
}

This is a configuration example. Enter the real key only in the local credentials form, then save and enable the connector. Copying only the URL does not authenticate.

WorkBuddy official configuration documentation

3. Verify with a read-only request

Call Wenbo get_workspace to read browsers, extension versions, platform accounts and submissionModes only. Do not create, sync or publish content.

After receiving browser, version and account information, check that submissionModes includes draft_sync. Select one browser when several are online and keep the same deviceId for related calls.

4. Explicitly request draft sync

Read workspace capabilities first. Only for platforms declaring draft_sync, sync my explicitly selected content with submissionMode: draft_sync. Do not publish. Report fieldResults, missingFields and draft persistence confirmation; a created job or partial field success is not a confirmed save.

A confirmed draft is not a publication. Saving is confirmed only when draft_synced and draftPersistence.state=confirmed are returned; missing fields still require author review. Unsupported platforms or formats are reported as unavailable. There is no DOM writing, direct publication or fallback.

Troubleshooting

• 401: check the key, mcp-key header and whether the client can read the environment variable.
• No browser found: keep the extension online and verify that the website, extension and client use the same Wenbo account.
• draft_sync not declared: update or inspect extension capabilities; never switch to automatic publishing as a workaround.

Other clients and tool reference