Bring RedNote & Douyin data into Codex: one MCP, one research skill
MediaClaw gives Codex 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. Describe the goal in plain language; it follows the method, and it can read your local knowledge base at the same time. Before any new collection it states the source and volume and waits for your go-ahead.
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 Codex 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.
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
Find low-follower, high-like accounts
“I just started an account and don't want to study 300k-follower creators. Find low-follower, high-like posts in this niche and tell me why they worked.” Four small accounts pulled from an 80-post sample, each with followers, top-post performance and what to learn.
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. Put it on a daily schedule 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
Write the findings back into your own knowledge base
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 core conclusions, theme signals, disagreements and unmet needs up front — and a reviewable diff before anything is written.
Install free extension
Getting connected: three steps, no terminal, no config file
OS detection, chip detection, runtime download and checksum verification are all handled by 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 Codex row. The prompt already carries the official source, the host's install commands and the repair steps — you do not need to read or edit it.
Install free extension
Step 2: Send it to Codex and let it install itself
Paste it into a new conversation as-is. It registers the official marketplace, installs the package, detects Windows/macOS/Linux and x64/ARM64, then fetches and verifies the matching runtime. No Node install, no terminal, no picking a .exe — and it lists everything it did when it finishes.
Read the setup guide
Step 3: Approve the pairing back in the extension
A pending device appears in the Agent access tab. Check the device name and fingerprint, hit Approve, and Codex re-checks the connection by itself — no need to reply “approved”. Each agent is approved separately, and revoking one leaves the others alone.
Read the setup guide
What actually gets installed
One install brings two pieces. Add your own files and the set is complete.
MCP server: gets the data
A standard MCP (STDIO) integration Codex calls directly — 40+ tools, no hand-written JSON config.
- 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
Listed in Codex as “MediaClaw content research and generation”, carrying 12 written methods it follows instead of improvising.
- 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 local knowledge base: says who you are
Obsidian, Notion, Lark, or plainly a Markdown folder. Platform evidence and your own business facts meet inside one task.
- Read your published posts first, then surface topics readers want that you have not covered
- If no real material backs a point, it says what is missing instead of padding with generics
- Each study is written back as Markdown, so you can query it three months later
Five things it must ask you first
Approving the pairing lets Codex 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 |
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 | Fully quit and reopen Codex for a new version to activate | |
| WorkBuddy | Send the prompt, it installs itself | Same flow as Codex | |
| 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
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. A task that takes fifteen minutes is not fifteen minutes of token burn.
It is a standard MCP integration over STDIO, but on Codex you never write config. Send it the install prompt copied from the extension and it registers the official source, installs the package, detects your OS and chip, and verifies the runtime.
One install brings both. The MCP server exposes 40+ tools that fetch data from the platforms; the content research skill supplies 12 written methods that tell Codex 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.
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.
In an existing MediaClaw conversation just say “upgrade MediaClaw Agent” and it starts right away: it refreshes the official source, installs, verifies the version and keeps your unfinished request. After install you must fully quit and reopen Codex: a running Codex won't load the new version, even in a new conversation.
It checks what you already have first — analyses in the extension, reports in the cloud AI Workspace, and local collection records — and only considers new collection when none of those cover it. Say “don't use MediaClaw”, “don't call tools” or “only use the material I gave you” and it won't call MediaClaw. Requests unrelated to content research and creation never trigger it.
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.
The capabilities are identical — same package, same MCP tools, same skill. Codex and WorkBuddy let the agent handle install and upgrades end to end. Doubao for Work has no automatic install entry yet, so you save a STDIO connector by hand under Skills · Connectors, and it does not auto-update.
Give Codex real RedNote and Douyin data today
Install the free extension, send the install prompt to Codex, and let it handle the rest.
Updated