Thread Analyzer MCP Server
Allows scraping and analyzing replies from any public Threads post, providing tools to fetch all replies, search by keyword, and get reply statistics.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Thread Analyzer MCP Serveranalyze replies on https://www.threads.com/@zuck/post/ABC123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What is this?
An MCP server that lets your AI assistant scrape a Threads post URL, then query and analyze the replies — all through natural conversation.
Instead of:
1. Manually open browser
2. Scroll through hundreds of replies
3. Copy-paste into spreadsheet
4. Manually look for patternsJust say:
"Analyze the replies on this Threads post: https://www.threads.com/@zuck/post/ABC123"
Your AI agent handles the rest.
Features
Network interception — Captures GraphQL API responses, not fragile CSS selectors that Meta randomizes
Anti-detection — Randomized scroll delays, stealth browser flags, custom User-Agent
4 MCP tools — Scrape, list, search, and get statistics on replies
Works with any MCP client — Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, and more
MCP Tools
Tool | Description |
| Scrape all replies from a public Threads post |
| Return all scraped replies with username and timestamp |
| Case-insensitive keyword search across replies |
| Reply count, top commenters, avg length, time range |
Quick Start
Prerequisites
Python 3.13+
uv package manager
Installation
git clone https://github.com/ethan-tsai-tsai/thread-analyzer.git
cd thread-analyzer
uv sync
uv run playwright install chromiumConfiguration
Add the server to your MCP client config:
{
"mcpServers": {
"thread-analyzer": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/thread-analyzer", "python", "server.py"]
}
}
}Add to your project's .mcp.json:
{
"mcpServers": {
"thread-analyzer": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/thread-analyzer", "python", "server.py"]
}
}
}Or run: claude mcp add thread-analyzer -- uv run --directory /absolute/path/to/thread-analyzer python server.py
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"thread-analyzer": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/thread-analyzer", "python", "server.py"]
}
}
}Go to Cursor Settings > MCP > Add new MCP Server, then add:
{
"mcpServers": {
"thread-analyzer": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/thread-analyzer", "python", "server.py"]
}
}
}Add to .vscode/mcp.json in your workspace:
{
"servers": {
"thread-analyzer": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/thread-analyzer", "python", "server.py"]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"thread-analyzer": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/thread-analyzer", "python", "server.py"]
}
}
}Standalone CLI
You can also use the scraper directly without MCP:
uv run python scraper.py "https://www.threads.com/@user/post/XXXXX"
# Options
uv run python scraper.py "URL" --output custom.csv --max-scrolls 50How It Works
┌─────────────┐ MCP (stdio) ┌──────────────┐ Playwright ┌─────────────┐
│ AI Client │ ◄──────────────────► │ server.py │ ◄──────────────► │ Threads.com │
│ (Claude, │ scrape_thread() │ (FastMCP) │ GraphQL API │ (Meta) │
│ Cursor...) │ get_all_replies() │ │ interception │ │
│ │ search_replies() │ replies.csv │ │ │
│ │ get_reply_stats() │ │ │ │
└─────────────┘ └──────────────┘ └─────────────┘You give your AI assistant a Threads post URL
AI calls
scrape_thread(url)via MCPServer launches headless Chromium, navigates to the post
Playwright intercepts GraphQL network responses containing reply data
Server parses replies (username, text, timestamp), saves to CSV
AI uses
get_all_replies(),search_replies(),get_reply_stats()to analyze
Anti-Detection
Technique | Purpose |
Custom User-Agent | Mimics real Chrome browser |
| Hides automation flag |
| Prevents Chromium detection |
Randomized scroll delays (1.5-4.5s) | Avoids behavioral fingerprinting |
Early stop on idle scrolls | Mimics natural browsing patterns |
Limitations
Public posts only — Cannot access private or restricted posts
Meta's anti-bot measures — Meta may block headless browsers; if scraping fails, try the standalone CLI in non-headless mode
GraphQL schema changes — Meta periodically changes their API structure; the parser in
scraper.pymay need updating
Contributing
Contributions are welcome! Please open an issue or submit a pull request.
License
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ethan-tsai-tsai/thread-analyzer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server