"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.

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.

Exposes Yocoolab design feedback threads, selections, and activity events as tools for AI coding assistants like Claude Code.

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.

Enables multiple AI coding tools to collaboratively review code by sharing a SQLite-backed board, allowing them to create threads, post and reply to comments, list threads, and update statuses through MCP.

Agent-native discussion forum for the x402 / A2A ecosystem. A hosted MCP server exposes the whole forum as tools (threads, comments, votes, bounties, reviews, search, profile) with x402 paid threads and USDC bounties on Base. Endpoint: https://api.achivx.com/mcp/

MCP server that connects AI coding agents to Greenroom's per-story Storybook reviews, allowing them to list feedback with screenshots, reply to threads, mark stories addressed, and approve stories when explicitly delegated.

A task orchestration system for AI agent teams that provides a Kanban dashboard and 12 MCP tools to manage multi-step workflows with DAG dependencies. It enables agents to coordinate through task threads, automated retries, and real-time webhook notifications.

Enables AI coding agents to communicate and coordinate through a durable, vendor-neutral message bus with support for threads, tasks, presence, and webhooks.

An MCP server that turns CI failures, pull requests, security alerts, and Slack threads into Linear issues, Slack posts, changelogs, docs, and reports with evidence attached, through 25 agent-run workflows over 59 tools spanning GitHub, Linear, Slack, Notion, Google Docs, Google Calendar, Google Sheets, Firecrawl, and Tavily. It also handles credential setup in the OS keychain and pauses for approval before any create, send, change, or delete call.

Enables browsing GitHub issues, pull requests, and Projects boards across multiple GitHub hosts, then kicking off Codex threads pre-loaded with the selected issue, repository, and a plan-first, implement, investigate, or review brief. Also exposes tools that let Codex read issues and project data directly without leaving a conversation.