"Threads" matching MCP servers:

Provides read-only access to public Threads.net profiles and threads via anonymous scraping, with tools for profile info, user threads, and session management.

MCP server for Meta's Threads API that enables publishing posts and reply chains, reading timelines and insights, and managing long-lived credentials with proactive refresh and safety checks.

Unofficial MCP server for Meta's Threads API. Enables LLMs like Claude to publish posts, manage replies, and track insights through the Model Context Protocol.

This server enables local access to official Meta Threads data, including latest posts, analytics insights, follower demographics, and guarded, approval-based publishing of posts and replies.

Enables AI agents to interact with Threads via MCP, including sub-80ms keyword search, full nested discussion tree extraction, replying to any external thread, publishing posts, fetching user profiles and threads, trending topics, and engagement actions like likes and reposts.

Enables AI assistants to manage a Threads posting schedule through natural language, allowing them to view, add, update, reschedule, and skip posts in a local CSV schedule.

Enables AI agents to interact with Meta Threads by fetching profile details, recent posts, post and account analytics, and conversation reply trees, as well as exporting posts as JSON for archiving or embedding.

Scrape and analyze replies from any public Threads post right from your AI coding agent.

MCP server for publishing threads to Threads and Twitter/X simultaneously from Claude Code. Journal your thoughts, convert them to viral threads, and post everywhere at once.

Automatically saves and restores project state when Claude threads hit token limits, ensuring seamless conversation continuity and preventing project fragmentation with intelligent name validation.

Thread Contract is a local runtime contract layer for AI coding-agent threads. It lets users pin explicit, thread-scoped rules without turning them into project policy or long-term memory.

Enables persisting chat-thread notes to SQLite with upsert semantics, allowing creation, update, retrieval, and listing of per-user threads via MCP tools.

Enables uploading local files to Slack with a message, supporting channels, DMs, threads, and file titles.

Enables AI chat sessions to exchange messages and structured data with each other, preserving provenance and conversation threads, so work in one chat can be reused in another without manual copying.

A read-only, date-aware MCP server that lets Claude Code (or any MCP client) search the UnknownCheats forum and read threads using your own logged-in session, labeling every result with a UTC date and age so stale offsets and signatures are obvious. Limits itself to reads, pins cookies to the forum domain, and throttles requests to keep traffic human-shaped.

A read-only Reddit MCP server that fetches threads, comments, and subreddits from the Arctic Shift archive over HTTP, requiring no Reddit account or API key.

Provides read-only access to Jira, enabling users to retrieve issue details, comment threads, linked-issue context, epic children, and JQL search results as compact Markdown.

Enables reading Slack channels, messages, and threads using the web interface via a persistent browser session, designed for guest users without API access. Does not send messages.

Provides comprehensive read/write access to Word documents, including comments, track changes, and reply threads.

LinkedIn prospect intelligence inside Claude. It automates the research behind outreach, not the sending: scrapes posts, profiles and comment threads into a local SQLite database, classifies what a person or company actually posts about, mines comment threads for people already describing your problem, and surfaces uncommon commonalities worth opening with.