Bring RedNote & Douyin data into Doubao for Work: one connector, one research skill
MediaClaw gives Doubao for Work two things: a RedNote (Xiaohongshu) and Douyin MCP server whose 40+ tools collect posts, videos, comments and account data and dedupe them into structured results, and a content research skill whose 12 written methods handle teardowns, topic picks and drafting. The only difference from Codex and WorkBuddy is the install: Doubao for Work needs you to save a local STDIO connector by hand under Skills · Connectors · Partners, and the agent itself prepares every field you have to fill in. After that, describe the goal in plain language.
You need the MediaClaw browser extension installed and an active membership first. Set the connector up on the same computer that runs the extension. The agent can only use capabilities you approved in the extension, and every page visit still happens in your own browser.
What one sentence gets you once Doubao for Work is connected
All six are real MediaClaw Agent runs. The prompts are copy-ready — swap what's in angle brackets for your own. Every host runs the same MCP tools and the same methods, so the output is identical; the chat window in these screenshots may not match yours, but what comes back does.
See who is winning: top posts ranked by likes
“Show me the top RedNote posts on <keyword> from the last six months and rank the representative ones by likes.” It organizes the sample it just collected and charts like counts, so which content actually earned engagement is visible at a glance.
Install free extension
Then pick a direction: turn the sample into topics you can write
Ask it to group the same sample by content direction, list representative posts for each, and suggest topics worth trying. Want to go deeper on one? Have it back-fill the body text and comments of those posts. The ranking and conclusions come from that sample, so they shift with the keyword and time range.
Install free extension
Mine a comment section for topics you can write
“Pull at least 300 comments from this post, analyse what readers want, and tell me which topics I can take.” 322 comments deduped to 280, 35.4% of them explicit needs, delivered as a prioritized topic list and a multi-sheet workbook.
Install free extension
See what a topic looks like across both platforms
“Check what new techniques people are posting about <keyword> on RedNote and Douyin lately.” It pins down which product the keyword means, reuses the existing RedNote sample, back-fills only Douyin, and groups recent patterns into 7 categories with examples.
Install free extension
Today's posts only — no last month's hits
“Show me RedNote posts about <keyword> published today.” 80 latest posts scanned as of 23:48, grouped by content direction with the current top performers listed. Run it daily and it becomes lightweight monitoring.
Install free extension
Tear down a video, then get a script you can shoot
“Why does this video keep people watching? How does the opening land and how does it build? Also turn it into a script I can shoot.” A precise teardown needs the transcript, so it asks first, extracts only after you confirm, then returns the structure plus a 90-second script.
Install free extension
Getting connected: four steps to one local connector
Doubao for Work has no automatic install entry yet, so you save the connector by hand. You do not have to work out what goes in it: the agent prepares the runtime files first, then hands you a list with the server name, transport, command, arguments and environment variables. Do this on the same computer that runs the MediaClaw extension, with the browser and extension open.
Step 1: Copy the Doubao install prompt from the extension
Open System settings → Agent access in the extension, turn on “Allow local agents to call MediaClaw”, expand “Connect Agent”, and hit Copy on the Doubao for Work row. Make sure you take that row — its prompt differs from the Codex and WorkBuddy ones.
Install free extension
Step 2: Send it to Doubao and let it produce the configuration list
Start a task in Doubao for Work and paste the prompt as-is. It prepares the runtime files, then lists the server name, transport, command, arguments and environment variables. That list is generated for your machine — keep it for the next step, and never copy paths out of a screenshot.
Read the setup guide
Step 3: Create the custom connector, fill it in and switch it on
Open Skills · Connectors · Partners in the sidebar, then New → New custom connector. Name the server mediaclaw, pick STDIO as the transport, copy the command and arguments from the list, and add the environment variables one row per pair. Save, wait for “Connector installed”, then check under My skills → Connectors that its toggle is on.
Read the setup guide
Step 4: Approve the pairing, then verify back in Doubao
A pending device appears in the extension's Agent access tab. Check that it is Doubao for Work and that the fingerprint matches the one Doubao showed you, then hit Approve — a green “Agent connected” banner does not count while a device is still pending. Back in Doubao, say “the connector is created and the extension approved the pairing, please re-check the connection”; it verifies with a real tool call and shows the welcome message.
Read the setup guide
What the connector actually brings in
One connector brings two pieces. Add your own files and the set is complete.
MCP server: gets the data
A standard MCP integration over STDIO that Doubao calls through the connector — 40+ tools, and the task decides which ones run.
- Collect RedNote and Douyin posts, videos, profile feeds and search results
- Back-fill details, pull comments, extract image text and transcripts
- Keyword scans, long-tail expansion, account scans, benchmark discovery
- Read collections, analyses and style profiles already saved in the extension
Research skill: knows what to do with it
12 written methods it follows instead of improvising, covering everything from “is this niche worth entering” to “is this draft ready to publish”.
- Research: keyword trends, long-tail demand, benchmark accounts, account strategy, recent hits, single-post teardown
- Creation: topic ideation, content briefs, drafting, style adaptation, evidence-to-content framing
- A self-check before delivery: is every claim backed, is any guess written as fact
Your own material: says who you are
MediaClaw supplies what is happening on the platforms; only your own notes and business facts say who you are. Give it both and the topics land inside what you can actually write.
- A topic is an intersection: readers want it ∩ you have not covered it
- If no real material backs a point, it says what is missing instead of padding with generics
- Each study is written back as a document, so you can query it three months later
Five things it must ask you first
Approving the pairing lets Doubao for Work connect to MediaClaw. It does not approve every collection that follows.
| Action | What it shows you first | After you confirm |
|---|---|---|
| Collect an account | A collection plan: target, fields, scope, batch count, risk level | It runs — and only the batches written into that plan |
| Video transcript | Which videos it will transcribe and how long each one is | Extraction starts; items already extracted are not extracted again |
| Bulk detail back-fill | Exactly what this round will back-fill | It opens the detail pages |
| Clear data | Blast radius: how many records, comments and transcripts, and the space freed | The deletion runs |
| Comment outreach | A recipient list and the message copy | You still confirm the send inside the extension |
Doubao for Work, Codex or WorkBuddy
All three hosts run the same package, the same MCP tools and the same skill. Only the install path and auto-update differ.
| Host | Install | Auto-update | Notes |
|---|---|---|---|
| Doubao for Work | Create a STDIO connector by hand; the agent prepares every field for you | No automatic install entry yet, so upgrades are redone manually | |
| Codex | Send the prompt, it installs itself | Fully quit and reopen the host for a new version to activate | |
| WorkBuddy | Send the prompt, it installs itself | Same flow as Codex |
Frequently Asked Questions
Codex and WorkBuddy have their own plugin managers, so the agent can install the package and register the tools end to end. Doubao for Work currently needs you to save a custom connector in its UI, which tells it where to launch the local MediaClaw tools from and how to connect to them. The install prompt makes Doubao prepare the runtime files and turn the required fields into a list — you just copy it across once.
No. The list is generated for your machine; copy it item by item. Two things to watch: if an argument is marked as blank, do not click Add and do not literally type “blank”; and the command paths and Node path in the tutorial screenshots are only examples — they differ on every computer, so never copy them.
Check three things in order. One: under My skills → Connectors, is the MediaClaw toggle on? Two: does the extension's Agent access tab still show a pending device — a green “Agent connected” banner does not count while one is waiting. Three: are the browser and extension running on the same computer as the connector? If all three are fine, ask Doubao to re-check the connection and it will verify with a real tool call.
No. On Codex and WorkBuddy you can say “upgrade MediaClaw Agent” in an existing conversation and the agent handles it. Doubao for Work has no automatic install entry, so after a new extension release you redo the install and connector configuration by hand. Either way you must fully quit and reopen the host — a running process will not hot-load a new version.
Less than you would expect. Collection, pagination and rate-limit cooldowns all run inside the extension and consume no host model quota — the extension hands back only structured results. Tokens go to three things: understanding the request, issuing calls and reading results, and the analysis and writing. It also reuses existing data before collecting anything new, and previews large payloads before paging into detail.
One connector brings both. The MCP server exposes 40+ tools that fetch data from the platforms; the content research skill supplies 12 written methods that tell Doubao how to analyse and write once the data is back. Tools without methods give you data with no conclusion.
Yes. The agent package cannot run on its own and does not replace the extension. Every page visit happens through the extension in your own browser, and the agent can only use capabilities you approved there.
Collection runs in your own browser using the sessions you are already logged into; the session is never handed to the agent. Never paste cookies, tokens, activation codes or device keys into a conversation, issue or log — the agent will not ask for them. Revoking one agent's authorization leaves the others alone.
No. Before any new collection it states the source, time range, volume, what it will read and the cost boundary, and waits for your agreement. Billable capabilities such as transcripts show an estimated credit cost and balance for a second confirmation. Silence is never treated as consent, and anything beyond the approved scope is asked again.
The browser extension itself is free to use. Agent access requires an active membership, and billable capabilities such as video transcripts need credits plus a confirmation before they run. Analysis, generation and reporting on the agent side cost no MediaClaw credits.
Give Doubao for Work real RedNote and Douyin data today
Install the free extension, send the prompt to Doubao, and save the connector it writes out for you.
Updated