threads-lyr
Provides read-only access to public Threads.net profiles and threads, including profile bio, follower/following/post counts, and recent threads with text, URL, creation time, and engagement metrics.
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., "@threads-lyrshow recent threads from @zuck"
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 it does
get_threads_profile— bio, follower/following/post counts for any public profileget_user_threads— recent public threads (text, url, created_at, engagement)close_session— release scrape clientsAgent-first CLI — AXI-compliant (
--list-tools,--tool-info,--json,--hook,--install-hook,--install-skill)Two MCP transports — stdio and streamable-http
Threads posts and profiles are public, so the client fetches threads.net/@username
directly — Chrome TLS impersonation gets through, no credentials required. Cloned from
facebook-lyr and stripped to Threads only.
Related MCP server: meta-threads-mcp
Why anonymous scraping?
The official Threads API requires Meta app registration and access tokens, and writing tools need authorized credentials. For reading public content, that's heavy machinery for a problem an anonymous fetch already solves.
curl_cffiwith Chrome TLS impersonation defeats JA3 fingerprint detection.Profiles and feeds are parsed from Threads' embedded JSON with a resilient deep-scan — no fragile selectors.
Tools are annotated
readOnlyHintso agents know not to attempt writes.
Quick install
./install.sh # or: uv sync
uv run threads-lyr --status # anonymous — always validDirect CLI tool execution
uv run threads-lyr get_threads_profile --username zuck
uv run threads-lyr get_user_threads --username zuck --limit 10
uv run threads-lyr get_user_threads --username zuck --limit 5 --json
uv run threads-lyr --list-toolsMCP server
Spawn with no args on a pipe (as Claude Code / other MCP clients do):
threads-lyr # starts the JSON-RPC stdio serverFor the streamable-http transport:
TRANSPORT=streamable-http PORT=8000 threads-lyrHonest platform limits
Read-only. Publishing on Threads requires the official Threads API — out of scope for anonymous scraping.
Anonymous. Only public profiles are reachable; private profiles return not-found/empty.
Layout
threads_mcp_server/
scraping/ curl_cffi Chrome-impersonation client + embedded-JSON parsers
tools/ FastMCP tool registration (threads_tools.py)
server.py FastMCP server assembly
cli_main.py AXI-compliant CLI
config/ layered config (CLI args > env > defaults)Visual proof
Profile | Threads feed | MCP tools |
|
|
|
Related CLI Tools
This project is part of a family of agent-friendly CLI tools for social platforms:
Tool | CLI | Repo |
| ||
Threads |
| |
| ||
| ||
| ||
Twitter/X |
| |
Discord |
| |
Telegram |
|
License
MIT — see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceA stdio MCP server for the official Threads API, enabling publishing, reading, moderation, insights, discovery, locations, and setup diagnostics.2MIT
- AlicenseAqualityCmaintenanceUnofficial MCP server for Meta's Threads API. Enables LLMs like Claude to publish posts, manage replies, and track insights through the Model Context Protocol.15MIT
- FlicenseAqualityCmaintenanceMCP server for the Threads API, enabling profile management, content reading, publishing, replies, and discovery through 26 tools.26
- AlicenseAqualityAmaintenanceEnables reading public X (Twitter) content like profiles, tweets, and search results via a stealth browser, without official API costs.11MIT
Related MCP Connectors
Browse and manage Reddit posts, comments, and threads. Fetch user activity, explore hot/new/rising…
Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.
Clean web reader for AI agents. Free remote read tier, optional x402 pay-per-call. No API keys.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/ishan-parihar/threads-lyr'
If you have feedback or need assistance with the MCP directory API, please join our Discord server


