X/Twitter tools for Claude Cowork and Claude Code
npx claudepluginhub wcfcarolina13/x-scraper-mcpRead X/Twitter posts, unroll threads, fetch user profiles, download media, and extract text from images via OCR.
An MCP (Model Context Protocol) server that reads X/Twitter posts, threads, and user profiles — directly inside Claude Code, Cursor, or any MCP-compatible client.
No Twitter API key required. No third-party services. No ads.
Built as a replacement for services like Unrollnow — paste an X link, get clean readable content.
| Tool | Description |
|---|---|
read_tweet | Fetch a single tweet. Returns text, media, polls, quotes, engagement stats, community notes. |
read_thread | Unroll a full thread into readable markdown. Walks up to the root and discovers children via syndication. Supports multi-URL input. |
read_user | Fetch a user profile — bio, follower counts, join date, verification status. |
download_media | Download images/videos from a tweet to local filesystem. Returns file paths, dimensions, and sizes. |
analyze_media | Extract text from images using OCR (Tesseract.js). Accepts local files or URLs. |
All tools accept any X/Twitter URL format:
https://x.com/user/status/123https://twitter.com/user/status/123https://fxtwitter.com/user/status/123https://vxtwitter.com/user/status/123@username or bare username (for read_user)123456789git clone https://github.com/wcfcarolina13/X-Scraper-MCP.git
cd X-Scraper-MCP
npm install
Add to your project's .mcp.json (or ~/.claude/settings.json for global access):
{
"mcpServers": {
"fxtwitter": {
"command": "npx",
"args": ["tsx", "/path/to/X-Scraper-MCP/src/index.ts"]
}
}
}
Replace /path/to/X-Scraper-MCP with the actual path where you cloned the repo.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"fxtwitter": {
"command": "npx",
"args": ["tsx", "/path/to/X-Scraper-MCP/src/index.ts"]
}
}
}
Once configured, the tools are available in any Claude conversation:
Read a single tweet:
"Read this tweet: https://x.com/jack/status/20"
Unroll a thread:
"Unroll this thread: https://x.com/user/status/123456"
Read a profile:
"Who is @elonmusk on X?"
Download media from a tweet:
"Download the images from this tweet to /tmp/media: https://x.com/user/status/123"
OCR an image:
"Analyze the text in /tmp/media/123_0.jpg"
read_thread uses three strategies to assemble a complete thread:
replying_to_status links to find the thread root.Best practice: If you have the last tweet in a thread, provide that URL — walking up is 100% reliable. If you only have the first tweet, syndication discovery handles it for recent threads.
# Single URL
read_thread("https://x.com/user/status/111")
# Multiple URLs for guaranteed coverage
read_thread("https://x.com/user/status/111, https://x.com/user/status/222, https://x.com/user/status/333")
Uses the free FxTwitter API — the same backend that powers fxtwitter.com embed links. No authentication needed, no rate limits enforced (just don't abuse it).
For thread child discovery, falls back to Twitter's syndication timeline which serves embedded tweet widgets and exposes recent tweet IDs for public accounts.
All output is clean markdown:
### Tweet by @user (Display Name)
The tweet text here...
**Photos:** 2 image(s)
- https://pbs.twimg.com/media/xxx.jpg (1024x768)
- https://pbs.twimg.com/media/yyy.jpg (1024x768)
*1.2K likes · 340 retweets · 56 replies · 45.2K views*
*Wed Feb 19 04:17:27 +0000 2026*
*Source: Twitter for iPhone*
*URL: https://x.com/user/status/123*
For richer Twitter data (search, trending, advanced thread traversal), you can add ScrapeBadger MCP alongside this server:
{
"mcpServers": {
"fxtwitter": {
"command": "npx",
"args": ["tsx", "/path/to/X-Scraper-MCP/src/index.ts"]
},
"scrapebadger": {
"command": "uvx",
"args": ["scrapebadger-mcp"],
"env": {
"SCRAPEBADGER_API_KEY": "your_key_here"
}
}
}
}
Get a free API key (1,000 credits) at scrapebadger.com.
RuFlo Marketplace: Claude Code native agents, swarms, workers, and MCP tools for continuous software engineering
No description available.
Code intelligence powered by a knowledge graph — execution flows, blast radius, and semantic search