"Threads" matching MCP servers:

An MCP server that exposes Threads CLI data for managing hierarchical threads, containers, and progress logs. It enables users to create, organize, and track task history while maintaining compatibility with the Threads CLI storage.

This MCP server provides a browser-based board for managing threaded feedback sessions with an agent, enabling users to respond to multiple review findings or questions at their own pace with quick replies and batched submission.

A local-first MCP server for reading, planning, scheduling, and publishing Meta Threads posts, with OAuth and Keychain integration.

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

MCP server for Slack that reads permalinks, threads, and channel history, and replies to threads or adds reactions using private browser-session tokens.

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.

MCP server that turns articles, transcripts, and markdown into LinkedIn carousel PDFs, Instagram PNGs, and Threads PNGs. Content in, slides out. No web UI, no cloud service.

Enables browsing Reddit, searching posts, reading comment threads and user history, with opt-in posting and voting through the Reddit API.

Checks a social post against a platform's real character limit before it ships — X bills every URL at 23 characters and weights non-Latin script at 2, while Bluesky and Mastodon count grapheme clusters. Covers X, X Premium, Bluesky, LinkedIn, Threads, Mastodon, and Discord, with no credentials and no network access.

An MCP server that enables a supervising OpenAI Codex agent to delegate bounded implementation tasks to isolated worker threads with enforced file scopes and verification, optionally running in parallel git worktrees.

Convert technical-drawing PDFs and engineering callouts between metric and imperial — values stamped in place, threads cross-referenced, shop-floor rounding.

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.

Enables peer-to-peer asynchronous conversation between Claude.ai and Claude Code instances via a shared file-based notebook, allowing them to leave messages, start threads, and organize by project.

Sift enables AI assistants to search all of Apple Mail locally at high speed, including bodies and PDFs, returning collapsed threads with quoted replies removed, without sending data anywhere.

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.

MCP server that reduces token consumption in AI coding assistants by up to 90% via structural reads, PreToolUse hooks, and tp-\* subagents.

Enables MCP-compatible coding harnesses to read Amp threads as Markdown, with pagination and filtering options, through a read-only interface.

A shared coordination layer for multiple AI coding assistants, exposing a persistent task queue, per-task message threads, and progress tracking via JSON files on disk.