Bring RedNote & Douyin data into WorkBuddy: one MCP, one research skill
MediaClaw gives WorkBuddy 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. Once it is connected you do not decide what to collect or memorise any command — say what you are working on and where you are stuck.
You need the MediaClaw browser extension installed and an active membership first. 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 WorkBuddy is connected
These are real MediaClaw Agent runs and the prompts are copy-ready. 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.
Turn one post's comment section into a topic list
A comment section looks full of demand until you try to read it one row at a time. Hand over the link: 322 comments dedupe to 280 distinct texts, 99 of them explicit needs (35.4%), grouped into tool cost / text version of videos / zero-to-one tutorials / can't-ship problems, then delivered as a prioritized topic list and a multi-sheet workbook.
Install free extension
See one topic across RedNote and Douyin at once
Scrolling both apps yourself, it is easy to mistake one creator's demo for an official new feature. Hand it over: it first pins down which product the keyword means, reuses the existing RedNote sample, back-fills only Douyin, then groups recent patterns into 7 categories with examples and changelog links.
Install free extension
Chasing a trend — today's posts only
“Show me RedNote posts about <keyword> published today.” 80 posts from that day scanned as of 23:48, grouped by content direction with the current top performers listed. Put that one line on a daily schedule and it becomes lightweight monitoring.
Install free extension
Findings land in your documents, not in a chat log
The one thing the extension cannot do alone. “File these comments into <knowledge base path> and put the conclusion at the top.” 1,000 comments land in the document with likes, region and timestamps, opening with core conclusions, theme signals, disagreements and unmet needs — and a reviewable diff before anything is written. Three months later you can still query that library.
Install free extension
Getting connected: three steps, no terminal, no config file
WorkBuddy supports fully automatic installation, same as Codex. You do two things: copy a prompt, and approve once.
Step 1: Copy the 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 WorkBuddy row. The prompt already carries the official source, WorkBuddy's plugin-manager commands and the repair steps — you do not need to read or edit it.
Install free extension
Step 2: Send it to WorkBuddy and let it install itself
Paste it into a new WorkBuddy conversation as-is. It registers the official marketplace through its own plugin manager, installs the package, detects Windows/macOS/Linux and x64/ARM64, and fetches and verifies the matching runtime. If an older installer left a conflicting mediaclaw MCP entry, it explains and removes it rather than leaving two.
Read the setup guide
Step 3: Approve in the extension, it re-checks itself
A pending device appears in the Agent access tab. Check the name and fingerprint, hit Approve. This run finished in 2m49s with “MediaClaw Agent (WorkBuddy)” authorized; it re-checked the connection on its own and walked through what you can hand it — no need to reply “approved”.
Read the setup guide
What actually gets installed into WorkBuddy
One install brings two pieces. They answer “where does the data come from” and “what order do I work in once it arrives” — your own files complete the set.
MCP server: where the data comes from
40+ tools sit in WorkBuddy's tool list over standard STDIO. Which ones it calls, and how often, follows from the task — you never specify them.
- Content: posts, videos, profile feeds, search results, comments
- Enrichment: detail back-fill, image text recognition, video transcripts
- Research: keyword scans and long-tail expansion, account scans, benchmark discovery
- Reuse: read collections, analyses and style profiles already saved in the extension
Research skill: what order to work in
12 fixed methods, covering everything from “is this niche worth entering” to “is this draft shippable”. It follows them rather than improvising once data lands.
- Judge first: keyword trends, long-tail demand, benchmark accounts, account strategy, recent hits
- Then take apart: a single post's angle, structure, phrasing and engagement signals
- Then produce: topics, content briefs, outlines, drafts, adapted to your style
- Self-check before delivery: is every claim backed, is a guess written as fact, is it too close to the source
Your files: why this could only be yours
A local Markdown folder is enough; Obsidian, Notion or Lark work too. MediaClaw knows what is happening on the platforms — only your library knows who you are.
- The overlap is the topic list: wanted on the platform ∩ never written by you
- When nothing in your files backs a point, it says what is missing instead of padding
- Each study lands back in your docs, so next time you query the library instead of re-collecting
Five things it must ask you first
Approving the pairing lets WorkBuddy 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 | A quote: credits per item, total, your balance, expiry | Extraction starts; items already extracted are not charged twice |
| 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 |
Codex, WorkBuddy or Doubao for Work
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 |
|---|---|---|---|
| Codex | Send the prompt, it installs itself | Same flow as WorkBuddy | |
| WorkBuddy | Send the prompt, it installs itself | Fully quit and reopen WorkBuddy for a new version to activate | |
| 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 |
Frequently Asked Questions
Give WorkBuddy real RedNote and Douyin data today
Install the free extension, send the prompt to WorkBuddy, and reopen it once when the install finishes.